[ 
https://issues.apache.org/jira/browse/SLING-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762697#comment-17762697
 ] 

Julian Reschke commented on SLING-4228:
---------------------------------------

Q: do we need insertion order or just stable ordering? (I don't see why we 
would need insertion order).

In the latter case, now that we are firmly beyond Java 7, we could move back to 
"HashMap()", and that should reduce the memory footprint.


> Multi-value sling:alias property test fails (ResourceResolverTest)
> ------------------------------------------------------------------
>
>                 Key: SLING-4228
>                 URL: https://issues.apache.org/jira/browse/SLING-4228
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>            Reporter: Bertrand Delacretaz
>            Assignee: Antonio Sanso
>            Priority: Minor
>             Fix For: Resource Resolver 1.1.10
>
>
> The ResourceResolverTest.test_resolve_with_sling_alias_multi_value 
> server-side integration test currently fails.
> I ran it on revision 1640140 of the resourceresolver and it passes, so it 
> looks like it's http://svn.apache.org/r1640141 that broke it, which points to 
> [~asanso] committing SLING-3844
> That test sets a multi-value sling:alias property on its test node with { 
> "kind", "enfant" } as values - I'm not sure how that's supposed to work but 
> the behavior has definitely changed.
> FWIW here's how to quickly run this server-side test:
> {code}
> $ cd launchpad/testing
> $ mvn clean launchpad:run
> # in another terminal
> $ curl -X POST 
> http://localhost:8888/system/sling/junit/org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest/test_resolve_with_sling_alias_multi_value.json
> ...
>     "failure": 
> "test_resolve_with_sling_alias_multi_value(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
>  expected:<\/[kind]> but was:<\/[enfant]>",
> {code}
> The ResourceResolverTest  can then be debugged out of the 
> launchpad/test-services module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to