You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Rory Douglas (JIRA)" <ji...@apache.org> on 2009/03/10 17:40:50 UTC
[jira] Commented: (SLING-882) SlingNodeStore.isDirty(item) always
returns false
[ https://issues.apache.org/jira/browse/SLING-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680530#action_12680530 ]
Rory Douglas commented on SLING-882:
------------------------------------
I think this is intentional. If you look at the setValue() implementation, you'll see that any changes made via dojo.api.Write API methods are immediately persisted via a POST to Sling, and there's no client-side caching of items, so nothing is ever really dirty. That's always why the save() method is a no-op. However, client-side caching & basic transactionality would be cool stuff to have - I've been running into cases where I need that recently.
> SlingNodeStore.isDirty(item) always returns false
> -------------------------------------------------
>
> Key: SLING-882
> URL: https://issues.apache.org/jira/browse/SLING-882
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Andreas Hartmann
> Priority: Minor
>
> isDirty: function(/* item? */ item) { console.log("isDirty");
> return false;
> },
> Is this on purpose, or is it just not implemented yet?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.