[SLING-4228] Multi-value sling:alias property test fails (ResourceResolverTest)

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Resource Resolver 1.1.10
• Component/s: ResourceResolver
• Assignee: Antonio Sanso
• Reporter: Bertrand Delacretaz
• Created: 08/Dec/14 15:06
• Updated: 19/Jan/15 10:41
• Resolved: 08/Dec/14 16:35

Description

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:

$ 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]>",

The ResourceResolverTest can then be debugged out of the launchpad/test-services module.

Issue Links

• is related to: SLING-3844 Resolver.map() spends too much time looking up sling:alias