[jira] [Closed] (SLING-2258) Request matching wrong resource when using same sling:alias for child/father nodes

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-2258.
-----------------------------------

    
> Request matching wrong resource when using same sling:alias for child/father nodes 
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-2258
>                 URL: https://issues.apache.org/jira/browse/SLING-2258
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.10
>            Reporter: Antonio Sanso
>            Assignee: Felix Meschberger
>             Fix For: JCR Resource 2.1.0
>
>         Attachments: SLING-2258-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 
> - add node "child" to node "test"
> - add node jcr:content to "child" 
> - add property sling:alias with value testAlias to the /test/child/jcr:content node 
> - call resolve for /test/testAlias/testAlias.html node 
> expected result: JcrNodeResource, type=..., superType=null, path=/test/child
> actual result: JcrNodeResource, type=..., superType=null, path=/test/jcr:content
> Also according to SLING-2246 jcr:content node cannot have an alias.
> 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