[jira] [Updated] (SLING-2076) Make MapEntries more dynamic
[ https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2076: Fix Version/s: (was: Resource Resolver 1.1.0) > Make MapEntries more dynamic > > > Key: SLING-2076 > URL: https://issues.apache.org/jira/browse/SLING-2076 > Project: Sling > Issue Type: Improvement > Components: ResourceResolver >Affects Versions: JCR Resource 2.0.10 >Reporter: Vidar S. Ramdal >Assignee: Vidar S. Ramdal > > In some scenarios it would be nice to be able to store mapping specs other > places than under /etc/map (for instance scattered around the > repository/resource tree, or in an external XML file). > It would be better if the entire map specification was provided by a separate > service. The current MapEntries would act as the default implementation. > Mailing list discussion: http://markmail.org/thread/5ww634sqarxtudks -- 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
[jira] [Updated] (SLING-2076) Make MapEntries more dynamic
[ https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2076: Fix Version/s: Resource Resolver 1.1.0 > Make MapEntries more dynamic > > > Key: SLING-2076 > URL: https://issues.apache.org/jira/browse/SLING-2076 > Project: Sling > Issue Type: Improvement > Components: ResourceResolver >Affects Versions: JCR Resource 2.0.10 >Reporter: Vidar S. Ramdal >Assignee: Vidar S. Ramdal > Fix For: Resource Resolver 1.1.0 > > > In some scenarios it would be nice to be able to store mapping specs other > places than under /etc/map (for instance scattered around the > repository/resource tree, or in an external XML file). > It would be better if the entire map specification was provided by a separate > service. The current MapEntries would act as the default implementation. > Mailing list discussion: http://markmail.org/thread/5ww634sqarxtudks -- 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
[jira] [Updated] (SLING-2076) Make MapEntries more dynamic
[ https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2076: Component/s: (was: JCR) ResourceResolver > Make MapEntries more dynamic > > > Key: SLING-2076 > URL: https://issues.apache.org/jira/browse/SLING-2076 > Project: Sling > Issue Type: Improvement > Components: ResourceResolver >Affects Versions: JCR Resource 2.0.10 >Reporter: Vidar S. Ramdal >Assignee: Vidar S. Ramdal > > In some scenarios it would be nice to be able to store mapping specs other > places than under /etc/map (for instance scattered around the > repository/resource tree, or in an external XML file). > It would be better if the entire map specification was provided by a separate > service. The current MapEntries would act as the default implementation. > Mailing list discussion: http://markmail.org/thread/5ww634sqarxtudks -- 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
[jira] [Updated] (SLING-2076) Make MapEntries more dynamic
[ https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2076: Fix Version/s: (was: JCR Resource 2.1.0) I'm unscheduling this from 2.1.0 to not block the release. I think we a new jcr resource release is overdue :) > Make MapEntries more dynamic > > > Key: SLING-2076 > URL: https://issues.apache.org/jira/browse/SLING-2076 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR Resource 2.0.10 >Reporter: Vidar S. Ramdal >Assignee: Vidar S. Ramdal > > In some scenarios it would be nice to be able to store mapping specs other > places than under /etc/map (for instance scattered around the > repository/resource tree, or in an external XML file). > It would be better if the entire map specification was provided by a separate > service. The current MapEntries would act as the default implementation. > Mailing list discussion: http://markmail.org/thread/5ww634sqarxtudks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
