You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2014/04/28 16:00:46 UTC

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

Konrad Windszus created SLING-3523:
--------------------------------------

             Summary: 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


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)