You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/10/07 11:21:44 UTC
[jira] Resolved: (JCR-1775) Transaction-safe versioning
[ https://issues.apache.org/jira/browse/JCR-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1775.
--------------------------------
Resolution: Fixed
Fixed in trunk. I have streamlined a number of the versioning operations and made sure that all versioning changes are persisted strictly before they get referenced in normal workspace content.
> 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
>
>
> 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.