You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Uwe Barthel (JIRA)" <ji...@apache.org> on 2015/11/21 01:04:11 UTC
[jira] [Commented] (JXPATH-118) wrongs xpath string from
pointer.asPath()
[ https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019139#comment-15019139 ]
Uwe Barthel commented on JXPATH-118:
------------------------------------
Open pull request: [JXPATH-118: Add test attached on JIRA item.|https://github.com/apache/commons-jxpath/pull/7].
The test passed on current trunk.
Thanks to [~mhaller] and [~vivodamichele@hotmail.com] for providing the original test sources.
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)