[
https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038582#comment-16038582
]
Tomek Rękawek commented on SLING-848:
-------------------------------------
[~reschke]
bq. Source, please. All I can see in RFC 3986 is that ";" is in the reserved
set.
Sorry, you're right, RFC doesn't explicitly define this form of ;key=val
parameters, it's up to the application developers. Nevertheless, we've defined
such format in this JIRA.
bq. we have to be a little bit pragmatic here and not break people's code again.
Please notice that the parameters have worked in this way (looking for the
equals sign or passing the path as-is if it can't be found) for two years now,
since this issue has been resolved.
I think that the Alex'es example ({{parent.addNode("something;else")}}) is not
exact - it should include the equals sign somewhere. [~alexander.klimetschek] -
could you confirm if the example you've provided is really a way to reproduce
this issue?
> 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: API, JCR, ResourceResolver
> Affects Versions: JCR Resource 2.0.2
> Reporter: Carsten Ziegeler
> Assignee: Tomek Rękawek
> Fix For: JCR Resource 2.5.0, API 2.9.0, Resource Resolver 1.2.0
>
> Attachments: SLING-848-metadata.patch
>
>
> 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.15#6346)
