[
https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15748621#comment-15748621
]
Bertrand Delacretaz commented on OAK-5260:
------------------------------------------
bq. I have used both ANTLR [9] and JavaCC in the past, but I find hand-written
parsers [1]-[8] to be easier to write and maintain.
Fair enough, and whoever does the job decides anyway! I guess the key is to
have sufficient test coverage to be confident in making changes, which is not
currently the case here IIUC.
> 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)
