[
https://issues.apache.org/jira/browse/SLING-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston resolved SLING-1129.
-------------------------------
Resolution: Won't Fix
This was one of my worse ideas.
The extension mechanism was to allow virtualization of URL space relative to
JCR space, on the face of it a good idea, but it abuses some fundamentals of
JCR, re-abstracts some of the JCR concepts and opens a pandora's box of
problems for http clients and implementation. IMVHO this should be closed as
wont fix, as there are better ways to do the above using the
JcrResourceResolver as it stands.
> Patch to make it easier to extend JcrResourceResolver2 and its factory.
> -----------------------------------------------------------------------
>
> Key: SLING-1129
> URL: https://issues.apache.org/jira/browse/SLING-1129
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.4
> Reporter: Ian Boston
> Fix For: JCR Resource 2.0.8
>
> Attachments: SLING-1129.diff
>
>
> At the moment, its hard if not impossible to extend the functionallity of the
> JcrResourceResolver2 and its Factory without succumbing to the dangerous
> practice of duplicating and patching implementation code.
> The patch to follow add some small extension points that makes it possible to
> extend the Factory as a component, and the JcrResourceResolver2 itself. It
> make no changes to functionality or API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
