[
https://issues.apache.org/jira/browse/JCR-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644713#action_12644713
]
Jukka Zitting commented on JCR-1775:
------------------------------------
The XA case should also be fixed as of revision 710047. The sequence of saves
for a checkin/checkout operation within an XA transaction is now:
VERSION_: {#addedStates=14, #modifiedStates=3, #deletedStates=0,
#modifiedRefs=0}
DEFAULT_: {#addedStates=0, #modifiedStates=3, #deletedStates=0, #modifiedRefs=0}
VERSION_: {#addedStates=0, #modifiedStates=0, #deletedStates=0, #modifiedRefs=1}
All tests (including a massive random/parallel test suite I ran over the
weekend) pass.
> Transaction-safe versioning
> ---------------------------
>
> Key: JCR-1775
> URL: https://issues.apache.org/jira/browse/JCR-1775
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core, transactions, versioning
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 1.5.0
>
>
> I've been working on a partial fix to JCR-630. Instead of implementing fully
> transactional versioning (i.e. a checkin will disappear when a transactin is
> rolled back), I'm ensuring that all versioning operations within a
> transaction will leave the version store in a consistent state even if the
> transaction otherwise fails at any point.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
