You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "David Croé (JIRA)" <ji...@apache.org> on 2008/02/08 15:27:13 UTC
[jira] Created: (JXPATH-118) wrongs xpath string from
pointer.asPath()
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é
Hello !
after playing around awhile with JXPath and Jdom i guess i've found a bug:
when trying to iterate of 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JXPATH-118) wrongs xpath string from
pointer.asPath()
Posted by "Mike Haller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Haller updated JXPATH-118:
-------------------------------
Attachment: JXPath118Test.java
Test file proving JXPATH-118, JXPath returning wrong asPath().
JXPath returns three times the same asPath value, although it should be different for three different fields.
> 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é
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JXPATH-118) wrongs xpath string from
pointer.asPath()
Posted by "Matt Benson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Benson resolved JXPATH-118.
--------------------------------
Resolution: Cannot Reproduce
I have tried this using jdom 1.1 and cannot reproduce it. I am not using JDK 6 (I use OS X) although I wouldn't expect that to be the source of your problem. Please reopen this issue when you can submit a test case.
> 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é
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JXPATH-118) wrongs xpath string from
pointer.asPath()
Posted by "Matt Benson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567127#action_12567127 ]
Matt Benson commented on JXPATH-118:
------------------------------------
This does look strange. Can you provide a sample document that triggers this?
> 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é
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (JXPATH-118) wrongs xpath string from
pointer.asPath()
Posted by "Matt Benson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Benson reopened JXPATH-118:
--------------------------------
> 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é
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JXPATH-118) wrongs xpath string from
pointer.asPath()
Posted by "David Croé (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Croé updated JXPATH-118:
------------------------------
Description:
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
was:
Hello !
after playing around awhile with JXPath and Jdom i guess i've found a bug:
when trying to iterate of 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
> 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é
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JXPATH-118) wrongs xpath string from
pointer.asPath()
Posted by "Emmanuel Bourg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JXPATH-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Bourg updated JXPATH-118:
----------------------------------
Fix Version/s: post-1.3
> 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: post-1.3
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.