[
https://issues.apache.org/jira/browse/SLING-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-1332.
--------------------------------------
Assignee: Felix Meschberger
Resolution: Fixed
Add support for multi-value sling:alias properties for resource resolution.
Mapping a resource will always use the first value of a multi-value sling:alias
property. (Rev. 985108)
> Support multi-value sling:alias resolution
> ------------------------------------------
>
> Key: SLING-1332
> URL: https://issues.apache.org/jira/browse/SLING-1332
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.8
>
>
> Currently, only a single sling:alias value for a resource is honoured, even
> though the sling:alias is defined as both a single-value and multi-value
> property [1].
> To reproduce:
> 1. Create a node at /node
> 2. Set a multi-value sling:alias property on /node, with values "alias1" and
> "alias2"
> 3. Browse to http://localhost:8080/alias2
> Expected result:
> - The resource at /node is returned
> Actual result:
> - A 404 not found. Still, browsing to /alias1 returns the /node resource.
> Mailing list discussion:
> http://n3.nabble.com/Multi-value-sling-alias-td140425.html#a140425
> [1]
> http://svn.apache.org/viewvc/sling/trunk/bundles/jcr/resource/src/main/resources/SLING-INF/nodetypes/mapping.cnd?view=markup#l32
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
