You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/10/03 17:36:35 UTC
DO NOT REPLY [Bug 3942] New: -
XPathAPI doesn't work on Relative Path anymore
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3942>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3942
XPathAPI doesn't work on Relative Path anymore
Summary: XPathAPI doesn't work on Relative Path anymore
Product: XalanJ2
Version: 2.2.x
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Critical
Priority: Other
Component: org.apache.xpath
AssignedTo: xalan-dev@xml.apache.org
ReportedBy: ken_ting@lodestarcorp.com
I have been using XPathAPI.selectSingleNode(mynode, "..") to retrieve the
parent node of NODE mynode.
For instance, mynode is referring to /root/level1/level2/@level3,
Using the above method always returns me a NODE referring to /root/level1/level2
with XALAN version released in March, 2001.
I downloaded the latest XALAN-j_2_2_D10, calling the same method simply returns
NULL.
We use a lot of XPathAPI.selectSingleNode(mynode, myxpath) while myxpath is
relative path such as ../, ./ etc. and it's been working great!
Thank you and looking forward to the fix.
Kenneth Ting
Lodestar Corp
ken_ting@lodestarcorp.com
713-292-2511