[
https://issues.apache.org/jira/browse/SLING-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-2319:
----------------------------------
Component/s: ResourceResolver
> Make the description of the JCR Resource Resolver configuration for
> resource.resolver.mapping less confusing
> ------------------------------------------------------------------------------------------------------------
>
> Key: SLING-2319
> URL: https://issues.apache.org/jira/browse/SLING-2319
> Project: Sling
> Issue Type: Improvement
> Components: JCR, ResourceResolver
> Affects Versions: JCR Resource 2.0.8
> Reporter: Thierry Ygé
> Assignee: Justin Edelson
> Priority: Minor
> Fix For: Resource Resolver 1.0.0
>
>
> If I go to the OSGi configuration of the JCR Resource Resolver to the entry
> for resource.resolver.mapping it says in the description that the format of
> each entry is <incomingURLPrefix><op><outgoingURLPrefix>. It is very
> confusing what is meant by incoming and by outgoing.
> The internal path is always on the left and the external one on the right.
> But if you go to the config Manager, the description of the JCR Resource
> Resolver is wrong. It reads "Form ist
> <externalURLPrefix><op><internalURLPrefix>", implying that the external one
> would be on the left. So the description is rather confusing.
> Therefore the operator ">" and "<" is exactly the wrong direction, because
> ">" does indeed mean incoming requests (but since the internal form stands on
> the right the arrow points in the wrong direction). Please fix the
> description and also make the operator more intuitive (although this would
> break backwards compatibility)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
