[
https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michele Vivoda updated JXPATH-118:
----------------------------------
Attachment: JXPath118Test.java
I changed the test to use jdk 1.4, reordered the fields, JXPath passes the test
in my version. Fields seem to be sorted alphabetically (being no defined
order?). The issue could be about model.jdom, while the test deals with beans.
> wrongs xpath string from pointer.asPath()
> -----------------------------------------
>
> Key: JXPATH-118
> URL: https://issues.apache.org/jira/browse/JXPATH-118
> Project: Commons JXPath
> Issue Type: Bug
> Affects Versions: Nightly Builds
> Environment: jdk 1.603 jdom 1.1
> Reporter: David Croé
> Fix For: 1.4
>
> Attachments: JXPath118Test.java, JXPath118Test.java
>
>
> Hello !
> after playing around awhile with JXPath and Jdom i guess i've found a bug:
> when trying to iterate over a html document parsed with jdom in this way:
> iterator = context.iteratePointers("/HTML[1]/BODY[1]/P[3]/TABLE[1]/TR/TD[3]");
>
> while(iterator.hasNext()){
> Pointer pointer = (Pointer)iterator.next();
> System.out.println("path:"+
> pointer.asPath()+":"+((Content)pointer.getNode()).getValue());
> }
> i get some wrong outputs.
> this shows sometime the wrong path for example:
> /HTML[1]/BODY[1]/P[3]/TABLE[1]/TR[2]/TD[1]
> but the value found is correct. I
> i would expect for example
> /HTML[1]/BODY[1]/P[3]/TABLE[1]/TR[2]/TD[3]
> Am i wrong or is this a bug !?
> greetings
> david croe
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
