Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <33002933.239811278513111369.JavaMail.jira@thor>
Date: Wed, 7 Jul 2010 10:31:51 -0400 (EDT)
From: "Stefan Guggisberg (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-2667) NodeReferences are lost when deleting
 and setting the same reference in the same save() cycle
In-Reply-To: <22985561.47381277415533380.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Stefan Guggisberg resolved JCR-2667.
------------------------------------

    Resolution: Fixed

fixed in svn revision 961388

> NodeReferences are lost when deleting and setting the same reference in t=
he same save() cycle
> -------------------------------------------------------------------------=
--------------------
>
>                 Key: JCR-2667
>                 URL: https://issues.apache.org/jira/browse/JCR-2667
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.6.1
>            Reporter: C=C3=A9dric Damioli
>            Priority: Critical
>             Fix For: 1.6.3
>
>
> I've written the following snippet to illustrate the issue :
>         Node root =3D session.getRootNode();
>        =20
>         Node a =3D root.addNode("a");
>         Node b =3D root.addNode("b");
>         b.addMixin("mix:referenceable");
>        =20
>         a.setProperty("p", b);
>        =20
>         root.save();
>        =20
>         System.out.println(b.getReferences().getSize());     // --> corre=
ctly returns 1
>        =20
>         a.setProperty("p", (Node) null);
>         a.setProperty("p", b);
>        =20
>         root.save();
>        =20
>         System.out.println(b.getReferences().getSize());    // --> return=
s 0 !
> When the ChangeLog is processed, added references are processed before de=
leted ones, so the persisted NodeReferences is finally wrong.
> I've set the priority of this issue to critical, because the persisted re=
ferences count is corrupted.
> A simple workaround is to first remove the property, then save, then add =
the property again, but it not satisfying.

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