commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele Vivoda (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JXPATH-188) Ancestor: not reverse axis in case of org.w3c.dom documents
Date Fri, 11 Dec 2015 00:01:10 GMT

     [ https://issues.apache.org/jira/browse/JXPATH-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michele Vivoda updated JXPATH-188:
----------------------------------
    Attachment: AncestorTest.java

I attach a modified test case that shows some issues:
- JXPath for beans do not use the document order for the nodes returned by a reverse axis
using {{selectNodes}} as opposed to JXPath for DOM and all the JAXP XPath implementations
tested 
- JXPath for DOM and for Beans do not use the document order for the single node returned
by a reverse axis using {{selectSingleNode()}} as happens for the JAXP XPath implementations

BTW, while at the moment is unclear if JXPath is Java 4 or 7 ;-) it is using Junit 3.8.1,
so please use that old syntax in tests, thanks.


> Ancestor: not reverse axis in case of org.w3c.dom documents
> -----------------------------------------------------------
>
>                 Key: JXPATH-188
>                 URL: https://issues.apache.org/jira/browse/JXPATH-188
>             Project: Commons JXPath
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Stefan Albrecht
>         Attachments: AncestorTest.java, AncestorTest.java
>
>
> XPath specifies the ancestor axis to be a reverse axis, thus I would expect that JXPath
delivers results along the reverse axis. This works, if applied to a context wrapping a poje,
but not if the context wraps an org.w3c.dom document.
> I attached a JUnit test for this (but, unluckily, not a patch...)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message