http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2650 *** shadow/2650 Tue Jul 17 01:00:11 2001 --- shadow/2650.tmp.20700 Tue Jul 17 01:00:11 2001 *************** *** 0 **** --- 1,43 ---- + +============================================================================+ + | Namespace axis resolution is not XPath compliant | + +----------------------------------------------------------------------------+ + | Bug #: 2650 Product: XalanJ2 | + | Status: NEW Version: 2.0.0 | + | Resolution: Platform: Other | + | Severity: Normal OS/Version: Other | + | Priority: Other Component: org.apache.xpath | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + As an example, take this simple XML document instance: + + <a:root xmlns:a="http://a/";> + <b:sub xmlns:b="http://b/"/> + <c:sub xmlns:c="http://c/"/> + </a:root> + + Now I would like to apply this sample XPath expression + (with the root node as the context node): + + ./child::a:root/child::*/namespace::* + + The resulting node set should be composed of: + + (a) 4 namespace nodes (a="http://a/"; and b="http://b/"; + from element b:sub and (a="http://a/"; and c="http://c/"; + from element c:sub respectively, as I would guess from + what is stated in the XPath data model ("Elements never + share namespace nodes ...") + + But, Xalan produces the resulting node set consisting of + + (b) 3 namespaces nodes (a="http://a/";, b="http://b/"; and + c="http://c/";, as invocations of several versions (2.2.D6, + 2.1.0, 2.0.0) of the Apache Xalan XPath engine show. + + Regards, Gregor
