[jira] [Assigned] (SLING-12025) ResourceResolver: different mapping when optimizedAliasResolution enabled

["Julian Reschke (Jira)" <ji...@apache.org>]

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

Julian Reschke reassigned SLING-12025:
--------------------------------------

    Assignee: Julian Reschke  (was: Joerg Hoh)

> ResourceResolver: different mapping when optimizedAliasResolution enabled
> -------------------------------------------------------------------------
>
>                 Key: SLING-12025
>                 URL: https://issues.apache.org/jira/browse/SLING-12025
>             Project: Sling
>          Issue Type: Task
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.10.0
>            Reporter: Joerg Hoh
>            Assignee: Julian Reschke
>            Priority: Major
>             Fix For: Resource Resolver 1.11.2
>
>
> I found that the there is a different behavior in case the "optimized alias resolution" is enabled.
> Setup:
> {noformat}
> * /content/jcr:content
>   + sling:alias=foobar
> {noformat}
> In my opinion the expected behavior is that the {{content}} resource is aliased and can be resolved via both {{/content}} and {{/foobar}}. You cannot alias the {{jcr:content}} node. Unfortunately there are no unit tests for that, and I just came across that behavior when I tried to write one.
> This works with the "optimized alias resolution" feature turned on, but if it's turned off, it does not work anymore, and you can resolve that resource only via its name. (In that case I assume that the jcr:content resource is aliased.)
> I created https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/105 to demonstrate this problem.
> Is my assumption about the behavior correct?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)