[SLING-2396] Make ResourceResolverFactory independent from JCR

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.1.0, API 2.2.4
• Fix Version/s: JCR Resource 2.2.0, API 2.3.0, Resource Resolver 1.0.0
• Component/s: API, JCR, ResourceResolver
• Assignee: Carsten Ziegeler
• Reporter: Vidar Skauge Ramdal
• Created: 02/Feb/12 13:26
• Updated: 16/Nov/12 06:18
• Resolved: 24/Aug/12 15:15

Description

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