You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/12/11 10:09:18 UTC
[jira] Created: (SLING-1232) Make the location of the resource
resolver mappings configurable
Make the location of the resource resolver mappings configurable
----------------------------------------------------------------
Key: SLING-1232
URL: https://issues.apache.org/jira/browse/SLING-1232
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR Resource 2.0.6
Reporter: Felix Meschberger
Fix For: JCR Resource 2.0.8
The location of the resource resolver mappings is currently hard-coded to be /etc/map.
To be able to prepare configurations and switch it into production or if an application has a different setup, it would be required to have this location configurable.
For backwards compatibility, the default location will remain /etc/map.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1232) Make the location of the resource
resolver mappings configurable
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-1232.
--------------------------------------
Resolution: Fixed
Assignee: Felix Meschberger
Updated site documentation with information on configurability of the /etc/map location.
Finally fixed unit test (mapRoot setup required) and adapted web console plugin to show (subset of) current configuration in Rev. 889624.
> Make the location of the resource resolver mappings configurable
> ----------------------------------------------------------------
>
> Key: SLING-1232
> URL: https://issues.apache.org/jira/browse/SLING-1232
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.8
>
>
> The location of the resource resolver mappings is currently hard-coded to be /etc/map.
> To be able to prepare configurations and switch it into production or if an application has a different setup, it would be required to have this location configurable.
> For backwards compatibility, the default location will remain /etc/map.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1232) Make the location of the resource
resolver mappings configurable
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789222#action_12789222 ]
Felix Meschberger commented on SLING-1232:
------------------------------------------
Introduced the "resource.resolver.map.location" (default /etc/map) configuration property in Rev. 889561
> Make the location of the resource resolver mappings configurable
> ----------------------------------------------------------------
>
> Key: SLING-1232
> URL: https://issues.apache.org/jira/browse/SLING-1232
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Felix Meschberger
> Fix For: JCR Resource 2.0.8
>
>
> The location of the resource resolver mappings is currently hard-coded to be /etc/map.
> To be able to prepare configurations and switch it into production or if an application has a different setup, it would be required to have this location configurable.
> For backwards compatibility, the default location will remain /etc/map.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.