[
https://issues.apache.org/jira/browse/SLING-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-3847:
----------------------------------
Description:
the MockResourceResolver implementation from testing/resourceresolver-mock uses
LinkedHashMap implementation to preserve node order. unfortuantely this is not
the case in the listChildren() method, which leads to mixing up the resource
order when listing children.
the patch attached fixes this.
was:
the MockResourceResolver implementation from testing/resourceresolver-mock uses
LinkedHashMap implementation to preserve node order. unfortuantely this is not
the case in the listChildren() method, which leads to mixing up the resource
order when listing children.
the patch attached fixed this.
Summary: MockResourceResolver: resource order is not preserved in
listChildren method (was: MockResourceResolver: resource order is not
preserved up in listChildren method)
> MockResourceResolver: resource order is not preserved in listChildren method
> ----------------------------------------------------------------------------
>
> Key: SLING-3847
> URL: https://issues.apache.org/jira/browse/SLING-3847
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing ResourceResolver Mock 0.2.0
> Reporter: Stefan Seifert
> Fix For: Testing ResourceResolver Mock 0.3.0
>
> Attachments:
> 140813_SLING-3847_MockResourceResolver_listChildrenOrder.java.patch
>
>
> the MockResourceResolver implementation from testing/resourceresolver-mock
> uses LinkedHashMap implementation to preserve node order. unfortuantely this
> is not the case in the listChildren() method, which leads to mixing up the
> resource order when listing children.
> the patch attached fixes this.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
