jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-1552) Concurrent property modification sometimes doesn't fail
Date Wed, 23 Apr 2008 15:09:21 GMT
Concurrent property modification sometimes doesn't fail

                 Key: JCR-1552
                 URL: https://issues.apache.org/jira/browse/JCR-1552
             Project: Jackrabbit
          Issue Type: Bug
            Reporter: Thomas Mueller

The following test prints "Success":

       Session s1 = ...
       Session s2 = ...
       s1.getRootNode().setProperty("b", "0"); // init with zero
       s1.getRootNode().setProperty("b", (String) null); // delete
       s1.getRootNode().setProperty("b", "1");
       s2.getRootNode().setProperty("b", "2");

However  if the line marked "... // delete" is commented out, 
it fails with the following exception:

cafebabe-cafe-babe-cafe-babecafebabe/{}b: the item cannot be saved
because it has been modified externally.
       at org.apache.jackrabbit.core.ItemImpl.getTransientStates(ItemImpl.java:246)
       at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:928)
       at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:849)

It should fail in all cases. If we decide it shouldn't fail, it needs to be documented.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message