[
https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059829#comment-13059829
]
Carsten Ziegeler commented on SLING-2076:
-----------------------------------------
As discussed in the mail thread, basically we have three options
a) Specify a service interface which returns the mapping - if such a service is
available use this, otherwise use the default implementation
b) Like a) but allow several implementations of the service and aggregate the
results
c) Instead of specifying a service interface to return the mappings, we could
specify a service interface for mapping
I prefer b) over a) - while c) looks tempting I see the ordering problem, e.g.
if we have two providers. Provider A provides mapping for /a and /a/b/c while
Provider B provides mappings for /a/b. Depending on which provider is called
first we get different results for /a/b/x and /a/b/c/z
We could invoke all providers and weight the results and then use the one with
the highest weight of course
However as noone came up with real use cases for c), I think we should go with
b)
> 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
> Fix For: JCR Resource 2.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
