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:19:58 GMT

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

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

> forbid silly names

Yes, I would prefer that, instead of what we have right now, and instead of adding more complex
rules such as "find matching }" or check for ":" and so on.

What we have right now is "kind of" broken because it results in very strange behavior. For
example:

{noformat}
session.getRootNode().addNode("{" + UUID.randomUUID());
> javax.jcr.ItemExistsException: {98dc892a-e9b4-4cc7-b692-936db4cea61e
{noformat}

Of course the error message is wrong, because how can it be possible that _that_ node exists.
The reason for this exception is that "\{" and everything behind that is currently ignored,
so that this is equivalent to:

{noformat}
session.getRootNode().addNode(".");
> javax.jcr.ItemExistsException: .
{noformat}



> 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