[SLING-1947] Remove dependency to JCR and make resource provider implementation easier

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: JCR Resource 2.0.6, File System Resource Provider 1.0.0, Bundle Resource 2.0.4
• Component/s: Extensions, JCR
• Assignee: Unassigned
• Reporter: Carsten Ziegeler
• Created: 21/Jan/11 13:02
• Updated: 22/Feb/13 16:09
• Resolved: 22/Feb/13 16:09

Description

Currently the resource provider implementations usually check if the resource points to a directory if the repository has a node at this location to allow to let the repository return this node as the directory resource.
This requires the implementations to adapt the resolver to a session, check if the node is available etc.

This looks like a workaround, creates an unnecessary dependency to JCR and might create problems in the future if the repository is not used as a provider or is not the root provider.

One solution would be to let the implementations return "nt:folder" and the resource resolver checks in this case the root provider if it has a resource at the same position and returns that one instead.

Issue Links

• duplicates: SLING-2541 General mechanism to chain resource providers