You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/08/15 18:19:18 UTC

[jira] [Resolved] (SLING-3847) MockResourceResolver: resource order is not preserved in listChildren method

     [ https://issues.apache.org/jira/browse/SLING-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-3847.
-------------------------------------

    Resolution: Fixed

Thanks for your patch, Stefan . It's applied

> 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
>            Assignee: Carsten Ziegeler
>             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)