[
https://issues.apache.org/jira/browse/JCR-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Draier updated JCR-2300:
-------------------------------
Status: Patch Available (was: Open)
> Does not retain order of child nodes on Orderable nodes when calling
> Node.update(srcWorkspace)
> ----------------------------------------------------------------------------------------------
>
> Key: JCR-2300
> URL: https://issues.apache.org/jira/browse/JCR-2300
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.6.0, 1.5.0
> Environment: Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed
> mode)
> Reporter: Cédric Mailleux
> Attachments: JCR-2300.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
