[ http://issues.apache.org/jira/browse/JCR-414?page=all ]
Nicolas Belisle updated JCR-414:
--------------------------------
Attachment: VersionHistoryTest.java
If you execute this a couple of times, you should notice that reads are not
consistent. Sometimes the version history is empty on the first print,
sometimes not.
Note also that successors are never updated correclty.
> jcr:successors property not persisted correctly within a transaction
> --------------------------------------------------------------------
>
> Key: JCR-414
> URL: http://issues.apache.org/jira/browse/JCR-414
> Project: Jackrabbit
> Type: Bug
> Components: versioning
> Versions: 1.0
> Environment: Java 5.0.
> Reporter: Nicolas Belisle
> Attachments: PropertyTest.java, VersionHistoryTest.java
>
> During a transaction, if you create a new version then read the version
> history the "jcr:successors" property is not updated. Note that
> "jcr:predecessors" is updated properly.
> Also, the version history is sometimes not propertly read. During the
> transaction, it might appear empty. This behavior in not consistent from one
> execution to another.
> After a restart of the repository, the version history and the
> "jcr:successors" property is read properly.
> * Tests cases will follow shortly.
> Thanks,
> Nicolas
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
