[
https://issues.apache.org/jira/browse/SLING-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2246.
-------------------------------------
Resolution: Fixed
Thanks for the patch, Antonio!
I think it makes sense to have a special case handling for jcr:content,
especially as
we already have this in the getProperty method.
I'Ve applied it in revision 1185732.
> 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
> Affects Versions: JCR Resource 2.0.10
> Reporter: Antonio Sanso
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.1.0
>
> 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
