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 2003/01/20 23:13:38 UTC
DO NOT REPLY [Bug 16276] -
Namespace Nodes are re-declared from parent elements
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=16276>.
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=16276
Namespace Nodes are re-declared from parent elements
------- Additional Comments From berin@ozemail.com.au 2003-01-20 22:13 -------
David,
Started looking at doing a fix for this last night, and got ran into a
problem. The NodeTester object is being used to test each node prior to
placing in the (from memory - no code in front of me) SubQueryResults list.
The NodeTester tests seem fairly basic, but is there a case where a namespace
definition might fail a test that the same local name will pass further up the
tree? (I know there are XPath expressions where this is the case, but not too
sure how detailed the NodeTester checks are.)
E.g.
<foo xmlns:bar="uri1">
<zoo xmlns:bar="uri2"/>
</foo>
Where some test that node tester does knocks out uri2, but would pass uri1. If
that's the case then I need to use a second NodeList to hold all found nodes
and refer to that as adding uri1 into the list would be incorrect, even though
the uri2 node was not selected.