[SLING-848] Support getting versioned resources by using uri path parameters

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.0.2
• Fix Version/s: JCR Resource 2.5.0, API 2.9.0, Resource Resolver 1.2.0
• Component/s: API, JCR, ResourceResolver
• Assignee: Tomek Rękawek
• Reporter: Carsten Ziegeler
• Created: 03/Feb/09 09:35
• Updated: 06/Aug/20 10:25
• Resolved: 19/Feb/15 12:37

Description

Getting versioned content should be support thorough uri path parameters, like /something/hello;v=1.1
For jcr based resources the value of the version should either point to a version name or label.

In order to not change our existing apis, we introduce a new utility method which removes all uri path parameters
and returns a map of these. Every resource provider could use this utility method and then decide to act on these
parameters.
If a requested version does not exists, a 404 is returned.
If the requested node does not directly point to a versionable node, the algorithm checks the parent hierarchy until a versionable node is found, and tries to get the version of this node and then goes down the path again. If the versionable node does not have the requested version or the child, a 404 is returned.

Issue Links

• is related to: SLING-4804 Semicolon parameters are not passed to the resource resolver
• is related to: SLING-4318 Sling resource API does not expose any versioning features - bounty offered.
• is related to: SLING-4437 MockJcrResourceResolverFactory should allow to register services dynamically.
• mentioned in: Page Loading...