[jira] [Updated] (SLING-3523) ResourceResolverImpl.mangleNamespace and unmangleNamespaces behave differently

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

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

Carsten Ziegeler updated SLING-3523:
------------------------------------

    Fix Version/s: Resource Resolver 1.1.2

> ResourceResolverImpl.mangleNamespace and unmangleNamespaces behave differently
> ------------------------------------------------------------------------------
>
>                 Key: SLING-3523
>                 URL: https://issues.apache.org/jira/browse/SLING-3523
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.1.0
>            Reporter: Konrad Windszus
>             Fix For: Resource Resolver 1.1.2
>
>
> Currently everything which smells like a namespace is automatically mangled during the call of ResourceResolver.map. But only registered namespaces are unmangled automatically during ResourceResolver.resolve. This should be fixed, so that mangling an arbitrary string and afterwards unmangling that, should always return the original string.
> You can see the according code in https://fisheye6.atlassian.com/browse/~br=trunk/sling/trunk/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverImpl.java?r=1590034#to1010.
> There is no namespace check during mangling.



--
This message was sent by Atlassian JIRA
(v6.2#6252)