jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
Date Tue, 20 Dec 2016 08:25:58 GMT

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

Thomas Mueller edited comment on OAK-5260 at 12/20/16 8:25 AM:
---------------------------------------------------------------

The intent in JCR 2 was to allow using qualified names. Using the "Clark" notation ("\{ns\}local")
was considered parseable, as long as ns was a valid URI (and valid URIs as per RFC 3986 are
always absolute, thus contain a scheme name).

Thus, parsing as qualified name should (IMHO) only be triggered if (a) there's a matching
closing "}" and there's a ":" in between (which wouldn't be allowed in a local name).

With that, I don't think the examples become ambiguous.


was (Author: reschke):
The intent in JCR 2 was to allow using qualified names. Using the "Clark" notation ("{ns}local")
was considered parseable, as long as ns was a valid URI (and valid URIs as per RFC 3986 are
always absolute, thus contain a scheme name).

Thus, parsing as qualified name should (IMHO) only be triggered if (a) there's a matching
closing "}" and there's a ":" in between (which wouldn't be allowed in a local name).

With that, I don't think the examples become ambiguous.

> Incorrect handling of subpaths with leading left curly bracket
> --------------------------------------------------------------
>
>                 Key: OAK-5260
>                 URL: https://issues.apache.org/jira/browse/OAK-5260
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: Bertrand Delacretaz
>            Assignee: Julian Sedding
>             Fix For: 1.6
>
>         Attachments: OAK-5260-jsedding.patch, OAK-5260.patch
>
>
> As per SLING-6383 it looks like the Oak name mapping causes for example getItem("/libs/{sub")
(with a left curly bracket in the path) to return the /libs node if that exists but the supplied
path does not.
> I'll attach a patch with a test that demonstrates this. 
> [~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section 3.2.5.1
Expanded Form could be involved, treating the left curly bracket in a special way that's not
appropriate here.



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

Mime
View raw message