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] [Commented] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
Date Tue, 20 Dec 2016 09:14:58 GMT

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

Thomas Mueller commented on OAK-5260:
-------------------------------------

[~julian.reschke@gmx.de] ok, but you would need to define what a "matching closing "}"" is.
If you need to count opening and closing {} cases, then you can't use a regular expression
to check for valid nodes. What about this:

* Register a namespace {{NamespaceRegistry.registerNamespace("x", "/\{:")}} (this is valid
right now).
* Register a namespace {{NamespaceRegistry.registerNamespace("y", ":")}} (this is valid right
now).
* Add node (a) named "\{/\{:}test" to the root node. (doesn't work right now, but I guess
should work).
* Add node (b) named "\{" to the root node. Not a qualified name. (doesn't work right now,
but according to you should be supported right?)
* Create a child node (c) to node (b) named "{:}test". Qualified name (works right now)
* Then node (c) will have the path "/\{/\{:}test". But that's the same path as node (a).



> 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