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 2002/05/16 20:28:39 UTC
DO NOT REPLY [Bug 9167] -
internally declared namespaces not resolved correctly by XPath processor
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=9167>.
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=9167
internally declared namespaces not resolved correctly by XPath processor
garyp@firstech.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From garyp@firstech.com 2002-05-16 18:28 -------
Andrew --
ApplyXPath is designed to be a sample of how to use the XPathAPI which is a
high level interface to the lower level XPath API that is actually used by
XalanJ. As a sample, it makes the assumption that the top level node of the
XML document specified in the first document will be used as the context for
resolving namespace prefixes. After all, in your example, if the b: prefix was
defined at different levels, which one should be used for the XPath specified
in the second argument?
So, ApplyXPath makes the assumption that it will use the top level node for its
namespace definition context which is why your second example is failing.
If you'd like it to work with the ApplyXPath sample, move the xmlns:b attribute
up to the top level element, ie the a:b element.
ApplyXPath is working as designed.
Gary