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 11:37:18 UTC
[jira] Commented: (SLING-1232) Make the location of the resource
resolver mappings configurable
[ 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.