You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2017/01/03 11:24:58 UTC
[jira] [Commented] (OAK-5260) Incorrect handling of subpaths with
leading left curly bracket
[ https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15794835#comment-15794835 ]
Davide Giannella commented on OAK-5260:
---------------------------------------
[~tmueller] could you please backport to 1.4? Cut date is 9th Jan.
> 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: Thomas Mueller
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
> Fix For: 1.5.17, 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)