Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1729574.1158530734064.JavaMail.jira@brutus>
Date: Sun, 17 Sep 2006 15:05:34 -0700 (PDT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-435) Node.update() does not work correct for
 SNS
In-Reply-To: <25081196.1147904765845.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-435?page=all ]

Jukka Zitting updated JCR-435:
------------------------------

    Fix Version/s:     (was: 1.1)

> Node.update() does not work correct for SNS
> -------------------------------------------
>
>                 Key: JCR-435
>                 URL: http://issues.apache.org/jira/browse/JCR-435
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.9, 1.0, 1.0.1
>            Reporter: Tobias Bocanegra
>         Assigned To: Tobias Bocanegra
>
> when node to be updated contains same-name-sibblings, only the first child is resepcted:
> W1: 
> /a
>   /b
>     - p1
>   /b
> W2:
> /a
>   /b
> now a W2."/a/b".update() iteratates over the child nodes of "a" and updates "b" twice.
> btw: in the case where property p1 is binary, and internally kept in a tmp-file, the tmp-file gets discarded and an exception is thrown when storing the changes. this might explain some issues discribed in JCR-428.

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