jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@day.com>
Subject Re: [jira] Commented: (JCR-533) failing Node.lock() might leave inconsistent transient state
Date Fri, 11 Aug 2006 09:18:37 GMT
Paco Avila (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/JCR-533?page=comments#action_12427471 ] 
> Paco Avila commented on JCR-533:
> --------------------------------
> I've reading the specification and can't find any reference to transient 
> session in Node.lock(). Do you mean that Node.lock() don't modify transient 
> session because it performs a Node.save() internally (there is no need to call save)?

Locking methods (as well as most versioning operations) in
fact do modify the transient space even if save() is called
immediately afterwards.
In other words: for the API user changes are persisted
after the call, he doesn't have to care about this. Still
the implementation temporarily modifies the transient space.
And actually, i think that this it's not quite correct.


View raw message