You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/06/14 14:47:42 UTC
[jira] [Updated] (SLING-2396) Make ResourceResolverFactory
independent from JCR
[ https://issues.apache.org/jira/browse/SLING-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-2396:
------------------------------------
Component/s: ResourceResolver
API
Affects Version/s: (was: JCR Resource 2.0.10)
JCR Resource 2.1.0
API 2.2.4
Fix Version/s: Resource Resolver 1.0.0
API 2.2.6
JCR Resource 2.1.2
> Make ResourceResolverFactory independent from JCR
> -------------------------------------------------
>
> Key: SLING-2396
> URL: https://issues.apache.org/jira/browse/SLING-2396
> Project: Sling
> Issue Type: Improvement
> Components: API, JCR, ResourceResolver
> Affects Versions: JCR Resource 2.1.0, API 2.2.4
> Reporter: Vidar S. Ramdal
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.1.2, API 2.2.6, Resource Resolver 1.0.0
>
>
> As discussed on http://markmail.org/thread/wp6cghi5nqprpusn we would like to create a ResourceResolverFactory implementation that is not dependent on JCR.
> This will make it easier to create custom ResourceResolverFactories, where things like domain mappings, vanity paths and resource provider resolution could will not have to be re-implemented.
> A whiteboard area for this has been created at http://svn.apache.org/repos/asf/sling/whiteboard/resourceresolverfactory
--
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