[ 
https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303202#comment-14303202
 ] 

Tomek Rękawek commented on SLING-848:
-------------------------------------

Actually, it adds a new marker interface to the ResourceProvider. I think it's 
compliant with the previous discussion:

{quote}
The sling resource resolver will extract uri parameters from the uri and pass 
them to the resource providers in an additional parameter. Currently the 
resource providers just get a path; we will extend this to be a path and a map 
of all uri parameters.
The map of uri parameters will later on also end up in the resource meta data.
{quote}

In the first version I modified the ResourceProvider interface, but Bertrand 
pointed out that it would be incompatible with existing ResourceProviders. 
That's why there is the new ParametrizableResourceProvider.

> Support getting versioned resources by using uri path parameters
> ----------------------------------------------------------------
>
>                 Key: SLING-848
>                 URL: https://issues.apache.org/jira/browse/SLING-848
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.2
>            Reporter: Carsten Ziegeler
>            Assignee: Bertrand Delacretaz
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to