You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2021/07/02 09:01:00 UTC
[jira] [Assigned] (SLING-10483) Incorrect mapping is returned when
a resourceResolver.map is called with all its aliases
[ https://issues.apache.org/jira/browse/SLING-10483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu reassigned SLING-10483:
---------------------------------------
Assignee: Robert Munteanu
> Incorrect mapping is returned when a resourceResolver.map is called with all its aliases
> ----------------------------------------------------------------------------------------
>
> Key: SLING-10483
> URL: https://issues.apache.org/jira/browse/SLING-10483
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.7.8
> Reporter: Santiago García Pimentel
> Assignee: Robert Munteanu
> Priority: Critical
> Fix For: Resource Resolver 1.7.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I think this might be related to https://issues.apache.org/jira/browse/SLING-10432
> When you have a path in which several nodes have some alias, resourceResolver.map(path) will return the wrong result in some cases.
> before SLING-10432 was fixed this happen more often, now the problem is reduced, but persist.
> eg.
> I have a path _/content/uw/ecrm/germany/www/de/home/laundry_
> of those _de_, _home_ and _laundry_ have aliases (dealias,homealias & laundryalias, respectively).
> when calling :
> {quote}resourceResolver.map("/content/uw/ecrm/germany/www/*dealias/homealias/laundryalias*")
> {quote}
> I get
> {quote}/content/uw/ecrm/germany/www/*de*/homealias/laundryalias
> {quote}
>
> Note *de* instead of *dealias.*
> It only happens when all map receives only aliases, then the first segment with alias is not used. i.e. if I remove the alias from *de*, *homealias* would then not be used
>
> calling rr.map() with just some of the paths using aliases, it seems to work fine now
--
This message was sent by Atlassian Jira
(v8.3.4#803005)