You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Vidar S. Ramdal (JIRA)" <ji...@apache.org> on 2011/05/10 15:02:47 UTC
[jira] [Created] (SLING-2076) Make MapEntries more dynamic
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.0.12
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
[jira] [Commented] (SLING-2076) Make MapEntries more dynamic
Posted by "Stefan Seifert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059840#comment-13059840 ]
Stefan Seifert commented on SLING-2076:
---------------------------------------
we've usecases for such an enhancement as well and would be happy with solution 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
[jira] [Commented] (SLING-2076) Make MapEntries more dynamic
Posted by "Carsten Ziegeler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129828#comment-13129828 ]
Carsten Ziegeler commented on SLING-2076:
-----------------------------------------
With SLING-2248 we added an OSGi event which should be sent whenever the mapping changes. So if we implement one of the solutions we have to
take care of this fact.
> 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.
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
[jira] [Commented] (SLING-2076) Make MapEntries more dynamic
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (SLING-2076) Make MapEntries more dynamic
Posted by "Carsten Ziegeler (Updated) (JIRA)" <ji...@apache.org>.
[ 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