Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <2749480.1150705352456.JavaMail.jira@brutus>
Date: Mon, 19 Jun 2006 08:22:32 +0000 (GMT+00:00)
From: "Tobias Bocanegra (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Assigned: (JCR-466) Modified values of REFERENCE property
 not stored correctly
In-Reply-To: <12765867.1150466309890.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

     [ http://issues.apache.org/jira/browse/JCR-466?page=3Dall ]

Tobias Bocanegra reassigned JCR-466:
------------------------------------

    Assign To: Tobias Bocanegra  (was: Stefan Guggisberg)

> Modified values of REFERENCE property not stored correctly
> ----------------------------------------------------------
>
>          Key: JCR-466
>          URL: http://issues.apache.org/jira/browse/JCR-466
>      Project: Jackrabbit
>         Type: Bug

>   Components: core
>     Reporter: David Garcia
>     Assignee: Tobias Bocanegra
>  Attachments: VersionManagerImpl_patch.diff
>
> Hi,
> In a multi-valued property of type REFERENCE, when its values are changed=
 most of the references are lost upon save().
> I can=C2=B4t attach a test case, but here is what I=C2=B4ve been able to =
test:
>    1. REFERENCE property has values [A, B] (A and B being node UUIDs).
>    2. A new reference (to node C) is appended to the array of values. New=
 value should be [A, B, C].
>    3. save().
>    4. Reopen session and reload.
>    5. New value is [C]. References to A and B are lost.
> I=C2=B4ve checked that the PersistenceManager gets a NodeReference object=
 with just one reference to node C, so the bug must be before the store().
> I don=C2=B4t know the internals of Jackrabbit, but I=C2=B4ve found a poss=
ible source of the problem in o.a.j.core.version.VersionManagerImpl#setNode=
References().
> When it "filters out" version storage references it also wipes out previo=
us references to A and B in the example above.
> One thing that has worked for me is to remove the not (!) in the conditio=
n:
>                 if (!hasItem(id.getParentId())) {
>                     refs.addReference(id);
>                 }
> But now even version storage references are persisted (and this shouldn=
=C2=B4t be happening?).
> Anyway, please check whether that solution is OK.
> A patch file to change the condition is attached.
> Thanks a lot.

--=20
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