[SLING-3420] Provide support for path operations

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Merger 1.0.0
• Fix Version/s: Resource Merger 1.1.0
• Component/s: Extensions
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 26/Feb/14 06:59
• Updated: 04/Sep/14 15:05
• Resolved: 01/Mar/14 09:45

Description

The resource merger merges resources from the search paths. This is very useful for reading/getting such resources.
However, as soon as you want to modify, create or delete such resources the code doing so needs more knowledge about how the resource merger works. And the code needs to switch from the mount path to a search path etc.

Therefore, the resource merging provider could directly implement the modifying resource provider:

• if the resource resolver is configured with less than two search paths, modifying is denied
• the last search path (e.g. by default /libs/) is considered to be unchangeable, so all operations are done on a higher search path

1. Create
This creates a node at the second last search path (e.g. /apps)
2. Delete
If there is a node at /libs, a node hiding this one is created at /apps. Otherwise the node at /apps is removed
3. Update
Creates/updates a node at /apps

All these methods need to check whether resource hiding is used and adjust the properties accordingly

Issue Links

• relates to: SLING-3423 ResourceMergerService API must allow custom merge paths