[
https://issues.apache.org/jira/browse/SLING-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127605#comment-13127605
]
Antonio Sanso commented on SLING-2246:
--------------------------------------
both the issue and the patch are based on the assumption that the jcr:content
node cannot have an alias . Can this assumption considered correct?
Should be the case I will also attach a patch containing more junit test for
JcrResourceResolverTest #testResolveResourceAliasJcrContent covering the map
cases.
For sure though having as result /testAlias/testAlias sounds wrong.
> Wrong mapping for nodes having sling:alias property
> ---------------------------------------------------
>
> Key: SLING-2246
> URL: https://issues.apache.org/jira/browse/SLING-2246
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Antonio Sanso
> Attachments: SLING-2246-asanso-patch.txt
>
>
> Step to reproduce the issue:
> - suppose you have a node having path /test
> - add node jcr:content
> - add property sling:alias with value testAlias to the /test/jcr:content node
> - call resolve#map for /test/jcr:content node
> expected result: /testAlias/_jcr_content
> actual result: /testAlias/testAlias
> patch to follow
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
