You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2009/01/08 13:02:59 UTC

[jira] Commented: (JCR-538) failing Node.checkin() or Node.checkout() might leave inconsistent transient state

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

angela commented on JCR-538:
----------------------------

added some modifications to the version methods with rev r732693 that check for successful completion of the operation.

however, from my point of view we should get rid of the transient modifications and use the same approach as other workspace level operations such as copy/clone. therefore leaving open.

> failing Node.checkin() or Node.checkout() might leave inconsistent transient state
> ----------------------------------------------------------------------------------
>
>                 Key: JCR-538
>                 URL: https://issues.apache.org/jira/browse/JCR-538
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, versioning
>         Environment: svn r430067
>            Reporter: Stefan Guggisberg
>            Priority: Minor
>
> an exception is thrown if any of the properties jcr:isCheckedOut, jcr:baseVersion or jcr:predecessors can not be successfully updated to reflect the new version state (e.g. due to lack of write privileges). however, the version was created and inconsistent transient state might still be pending.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.