Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <26257229.1172592485902.JavaMail.jira@brutus>
Date: Tue, 27 Feb 2007 08:08:05 -0800 (PST)
From: "Stefan Guggisberg (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-768) Node.getPath() will corrupt the session
In-Reply-To: <4836727.1172526125839.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-768?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Guggisberg resolved JCR-768.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.3

fixed as dominique suggested (svn r512296)

> Node.getPath() will corrupt the session
> ---------------------------------------
>
>                 Key: JCR-768
>                 URL: https://issues.apache.org/jira/browse/JCR-768
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1, 1.1.1, 1.2.1, 1.2.2
>         Environment: JDK 1.5, WinXP
>            Reporter: Frank Karlstr=C3=B8m
>         Assigned To: Stefan Guggisberg
>             Fix For: 1.2.3
>
>         Attachments: JackRabbitBugTest.java
>
>
> When calling Node.getPath() anytime, no mather if its before or after sav=
e, and when deleting nodes, the internal reference points to the wrong node=
s.=20
> The attached test will always fail with a javax.jcr.RepositoryException: =
/: cannot remove root node.=20
> We have seen other configurations where a node suddenly behaves as the an=
other node that has references and throw a reference exception, and yet oth=
er configurations where the node we though we deleted still exists, and ano=
ther node has now disappeared.
> I do not know what causes the bug,a good bet is perhaps the CachingHierar=
chyManager?. It was not present in Jackrabbit 1.0.1, but was introduced in =
1.1.
> Have also tested the latest release: 1.2.2, and the bug is still present =
there.

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