jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg" <stefan.guggisb...@gmail.com>
Subject Re: Node position after import
Date Tue, 07 Aug 2007 15:02:52 GMT
hi marcus

On 8/7/07, maka@onlaw.at <maka@onlaw.at> wrote:
> Hello List,
>
>
>
> I have found a behavior that does not seem to be consistent with the
> spec:
>
> After replacing a node with importXML using
> IMPORT_UUID_COLLISION_REPLACE_EXISTING the new node is not at the
> position of the replaced node (talking about the position among the
> siblings).
>
> The origininal node is removed, but the new node is created as the last
> child of the parent node, and not spec-compliant at the position of the
> replaced node.
>
>
>
> Is this a known bug?

no, please create a jira issue.

thanks
stefan

>
> Does anyone know a good workaround?
>
>
>
> Here how I use it:
>
>
>
> // assume Session s, Node n, String text
>
>         s.importXML(
>
>                         n.getPath(),
>
>                         new ByteArrayInputStream
> (text.getBytes("UTF-8")),
>
>
> ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING
>
>                    );
>
>
>
> And here a quote from the spec section 7.3.6
>
> ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING:
>
> If an incoming referenceable node has the same UUID as a node already
> existing in the workspace then the already existing node is replaced by
> the incoming node in the same position as the existing node.
>
>
>
> note "same position"
>
>
>
> Thank you for any hint,
>
>
>
> Regards,
>
> Marcus.
>
>

Mime
View raw message