[
https://issues.apache.org/jira/browse/OAK-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831360#comment-13831360
]
Thomas Mueller commented on OAK-1215:
-------------------------------------
OK, it works for Jackrabbit 2.x, but:
- Is it JCR 2.x spec compliant?
- Would it be possible to change the application?
- What is the impact if we don't provide compatibility with Jackrabbit 2.x here?
Providing Jackrabbit 2.x compatibility should be possible, but I would rather
not unless it is a really important use case. One solution would be: traversing
all child nodes and search for this property. That means it wouldn't use an
index for this case, and it would potentially read many nodes.
> Relative property paths don't work in XPath search expressions
> --------------------------------------------------------------
>
> Key: OAK-1215
> URL: https://issues.apache.org/jira/browse/OAK-1215
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Jeff Young
> Priority: Critical
> Attachments: relative-predicate-paths.tiff
>
>
> A search XPath of the form:
> {code}
> /jcr:root/etc/commerce/products//*[@size='M' or */@size='M']
> {code}
> returns:
> {code}
> Invalid path: *
> {code}
> (This works fine in Jackrabbit.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
