[
http://jira.codehaus.org/browse/JAXEN-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195562#action_195562 ]
Elliotte Rusty Harold commented on JAXEN-206:
---------------------------------------------
I've committed this patch and verified that I still have SVN access. Please verify that everything seems fine, and then close this bug. Thanks.
> bad order when context is a list of nodes at different depths
> -------------------------------------------------------------
>
> Key: JAXEN-206
> URL:
http://jira.codehaus.org/browse/JAXEN-206> Project: jaxen
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1.3
> Reporter: Brian Ewins
> Attachments: mismatch.patch
>
>
> As described by Elliotte on the list:
> Consider this:
> <z>
> <a>
> <b/>
> </a>
> <c/>
> </z>
> Suppose the list includes b and c in document order. c's parent
> precedes b's parent even though b precedes c
> When calling xpath.selectNodes(context) we can supply a list of nodes instead of a single node. By supplying a list containing b and c as described above, and selecting "parent::*", we should get the list [z, a] returned. Instead we get [a, z]. The reason is that DefaultLocationPath does not sort the nodes into document order when there is only a single step in the location path.
> Patch attached, including test case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
