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 <[email protected]>wrote: > On Tue, Sep 8, 2009 at 09:53, cedric mailleux<[email protected]> > 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 > [email protected] > -- Cedric Mailleux Software Architect Jahia Solutions France - www.jahia.com 18 rue d'Hauteville 75010 Paris, France +33 1 53 34 69 68 [email protected]
