jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1775) Transaction-safe versioning
Date Thu, 30 Oct 2008 08:23:44 GMT

    [ https://issues.apache.org/jira/browse/JCR-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643780#action_12643780
] 

Jukka Zitting commented on JCR-1775:
------------------------------------

The behaviour without transactions is as expected, even though it results in more store operations
than would be optimal. The XA case is wrong, and I've been trying to address that.

First I revisited my original plan of solving both the transaction issue and optimize the
number of stores in versioning operations by moving the NodeReferences that point to the version
store to the workspace persistence managers. This  would improve a number of things but breaks
the backreference checks for example when deleting versions. I had an idea to resolve that
issue but unfortunately it didn't work out too well in practice.

As a fallback I'm now solving just the XA case and leaving the multiple store operations in
place.

> 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.


Mime
View raw message