You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by cedric mailleux <ce...@jahia.com> on 2009/09/08 09:53:30 UTC
Does not retain order of child nodes on Orderable nodes when calling
Node.update(srcWorkspace)
Hi,
I have some orderable nodes :
[jnt:contentList] > nt:base
orderable
+ * (nt:base)
When I update a node in my workspace B with node.update(workspaceA), all the
properties/ node added-deleted are well propagated but the order of the
childs is not keeping the order from the source workspace.
I am using jackrabbit 1.6.0 (try also on 1.5.0 same issue).
When debugging in my source workspace in NodeImpl I see that
data.getNodeState().getChildNodeEntries() return a list well ordered but on
my target workspace the same call does not return a well ordered list but a
list of node oredred by creation (the last created the last in the list).
Try to work on a patch but does not find a way yet.
Any idea is welcome
Regards
--
Cedric Mailleux
Software Architect
Jahia Solutions France - www.jahia.com
18 rue d'Hauteville
75010 Paris, France
+33 1 53 34 69 68
cedric.mailleux@jahia.com
Re: Does not retain order of child nodes on Orderable nodes when
calling Node.update(srcWorkspace)
Posted by cedric mailleux <ce...@jahia.com>.
Hi,
I have created the jira :
https://issues.apache.org/jira/browse/JCR-2300
Regards,
Cedric
On Tue, Sep 8, 2009 at 12:00 PM, Alexander Klimetschek <ak...@day.com>wrote:
> On Tue, Sep 8, 2009 at 09:53, cedric mailleux<ce...@jahia.com>
> wrote:
> > When I update a node in my workspace B with node.update(workspaceA), all
> the
> > properties/ node added-deleted are well propagated but the order of the
> > childs is not keeping the order from the source workspace.
>
> From looking at the javadocs and the spec (both jsr170 and jsr283
> final draft), I can't find that it is explicitly mentioned whether
> ordering should be supported upon node update/merge or not. But
> following common sense, if the parent node is defined as orderable,
> this should be the case, regardless how the child nodes are created or
> updated.
>
> Could you file a bug for that?
>
> http://jackrabbit.apache.org/issue-tracker.html
>
> Regards,
> Alex
>
> --
> Alexander Klimetschek
> alexander.klimetschek@day.com
>
--
Cedric Mailleux
Software Architect
Jahia Solutions France - www.jahia.com
18 rue d'Hauteville
75010 Paris, France
+33 1 53 34 69 68
cedric.mailleux@jahia.com
Re: Does not retain order of child nodes on Orderable nodes when
calling Node.update(srcWorkspace)
Posted by Alexander Klimetschek <ak...@day.com>.
On Tue, Sep 8, 2009 at 09:53, cedric mailleux<ce...@jahia.com> wrote:
> When I update a node in my workspace B with node.update(workspaceA), all the
> properties/ node added-deleted are well propagated but the order of the
> childs is not keeping the order from the source workspace.
>From looking at the javadocs and the spec (both jsr170 and jsr283
final draft), I can't find that it is explicitly mentioned whether
ordering should be supported upon node update/merge or not. But
following common sense, if the parent node is defined as orderable,
this should be the case, regardless how the child nodes are created or
updated.
Could you file a bug for that?
http://jackrabbit.apache.org/issue-tracker.html
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com