sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-2092) Support /etc/map setups equivalent to Resource Resolver URL Mapping configuration
Date Wed, 01 Jun 2011 21:50:47 GMT

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

Felix Meschberger resolved SLING-2092.
--------------------------------------

    Resolution: Fixed

Fixed in Rev. 1130315 as described

> Support /etc/map setups equivalent to Resource Resolver URL Mapping configuration
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-2092
>                 URL: https://issues.apache.org/jira/browse/SLING-2092
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.10
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JCR Resource 2.0.12
>
>
> It is currently not possible to create a configuraiton structure in /etc/map to do the
same as is possible with URL Mapping in Resource Resolver configuration.
> For example: The URL Mapping configuration /content/sample/-/sample/ generates the following
entries in the internal data structures:
>    Resolution:  ^[^/]+/[^/]+/mosaic/   -->  /content/mosaic/ (internal)
>    Mapping: ^/content/mosaic/   -->  /mosaic/ (internal)
> Trying to do this with /etc/map content like this:
>     /etc/map
>          + ANY  - sling:match = [^/]+
>               + ANY  - sling:match = [^/]+
>                     + sample  - sling:internalRedirect = /content/sample/
> will lead to the following internal data structures:
>    Resolution:  ^[^/]+/[^/]+/mosaic/   -->  /content/mosaic/ (internal)
>    Mapping: ^/content/mosaic/   -->  [^/]+/[^/]+/mosaic/ (internal)
> This is obviously not a desired Mapping entry. On the other hand, assuming that "[^/]+/[^/]+"
stands for any scheme and any host:port we could just as well remove that from the internal
data structures for mapping when building the internal data structures and thus get the correct
expecte results.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message