[SLING-1193] Extend Resource interface and provide AbstractResource base class

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Servlets Resolver 2.0.8, Scripting Core 2.0.10, JCR Resource 2.0.6, Engine 2.0.6, API 2.0.8
• Fix Version/s: Servlets Resolver 2.1.0, Scripting Core 2.0.14, JCR Resource 2.0.8, File System Resource Provider 1.0.2, Bundle Resource 2.0.6, Engine 2.1.0, API 2.1.0
• Component/s: API, Engine, JCR, Scripting, Servlets
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 17/Nov/09 20:53
• Updated: 02/Nov/10 13:21
• Resolved: 13/Aug/10 07:02

Description

Currently the Resource interface has only bare bones API to access its own local attributes, like getPath() or getResourceType().

Accessing the resource in the context of its parent or its children is not currently possible and doing so requires getting the resource resolver out of the resource and asking the resource resolver.

For convenience, we should add the following methods:

getParent() – returns the parent resource (same as ResourceUtil.getParent(this))
getName() – returns the name of the resource (same as ResourceUtil.getName(this))
listChildren() – same as getResourceResolver().listChildren(this)
getChild(String) – same as getResourceResolver().getResource(this, path)
isResourceType(String) – same as ResourceUtil.isA(this, String)

The new AbstractResource class will implement these methods as indicated.

Implementors of the Resource interface are then advised to actually extend from the AbstractResource interface, which in the future will provide default implementations of any methods added to the Resource interface, if it makes sense.