[
https://issues.apache.org/jira/browse/JCR-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Heath updated JCR-3762:
----------------------------
Attachment: Test_JCR3762.java
> ISDESCENDANTNODE returns inconsistent and incorrect results when results
> include one or more shared nodes
> ---------------------------------------------------------------------------------------------------------
>
> Key: JCR-3762
> URL: https://issues.apache.org/jira/browse/JCR-3762
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Reporter: Dave Heath
> Attachments: Test_JCR3762.java
>
>
> When using ISDESCENDANTNODE in a JCR_SQL2 query, if the results include a
> shared node, the results often (but not always) include nodes which are not
> descendants of the given node (sometimes including the given node itself in
> the results).
> For example, I have the following nodes:
> /a1
> /b1/b2
> /c1
> I then share /b1 as /a1/b1, and run a query using ISDESCENDANTNODE(/a1). I
> expect to see /b1 and /b1/b2 in my results, which I do. But quite often the
> results also include /c1, sometimes they include /a1, and sometimes they
> include both.
> The attached test case shows this behavior in action. The test runs in a
> loop, so there is no need to re-run the test in case it succeeds the first
> time through.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
