Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <27796251.1155219194779.JavaMail.jira@brutus>
Date: Thu, 10 Aug 2006 07:13:14 -0700 (PDT)
From: "Stefan Guggisberg (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-538) failing Node.checkin() or
 Node.checkout() might leave inconsistent transient state
In-Reply-To: <29026468.1155202333909.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/JCR-538?page=comments#action_12427232 ] 
            
Stefan Guggisberg commented on JCR-538:
---------------------------------------

there's a similar issue with Node.restore(), Node.merge() and Workspace.restore() which all do finally call Session.save(). there's the risk of inconsistent transient state if this final save call fails for any reason (e.g. due to lack of write privileges). 

> failing Node.checkin() or Node.checkout() might leave inconsistent transient state
> ----------------------------------------------------------------------------------
>
>                 Key: JCR-538
>                 URL: http://issues.apache.org/jira/browse/JCR-538
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira