Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <180396659.1113485610640.JavaMail.jira@ajax.apache.org>
Date: Thu, 14 Apr 2005 15:33:30 +0200 (CEST)
From: "Dominique Pfister (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Resolved: (JCR-108) Node's childNodes out of sync after
 unsuccessful save()
In-Reply-To: <1621604267.1113471137498.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-108?page=history ]
     
Dominique Pfister resolved JCR-108:
-----------------------------------

    Resolution: Fixed

Thank you for reporting this issue. 

This issue was caused by the shared item states that were not reloaded when a PersistenceManager#store operation failed. Fixed by reloading item states from persistent storage in revision 161276.

> Node's childNodes out of sync after unsuccessful save()
> -------------------------------------------------------
>
>          Key: JCR-108
>          URL: http://issues.apache.org/jira/browse/JCR-108
>      Project: Jackrabbit
>         Type: Bug
>     Reporter: c keller
>     Assignee: Dominique Pfister
>     Priority: Minor

>
> If node.save() failes due to an exception in PersistanceManager.store(ChangeLog) a successive call to node.getNodes() will still contain a reference to the node which failed to be persisted.
> This is the case even after a call to refresh(false).
> You have to restart Jackrabbit in order to get rid of this reference
> UseCase in kind of dummy-code:
> node.addNode("new", "nt:unstructured");
> node.save();
> => ItemStateException from persistance
> node.refresh(false);
> Iterator itr = node.getNodes();
> while(itr.hasNext()) {
>    child = itr.nextNode();
> }
> => Exception: "Failed to build path to "new"

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira