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] Resolved: (JCR-1775) Transaction-safe versioning
Date Tue, 07 Oct 2008 09:21:44 GMT

     [ 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

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

View raw message