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=15361>. 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=15361 Using default namespaces in XML file will not currently work with XALAN [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal ------- Additional Comments From [EMAIL PROTECTED] 2002-12-13 15:49 ------- That Microsoft page cited merely gives a definition of the default namespace. For more detail, read my developerWorks articles, starting with: http://www-106.ibm.com/developerworks/library/x-nmspace.html Among other things, I show the "workarounds" needed to deal with default namespaces. Xalan is thoroughly tested with regard to handling of both default and prefixed namespaces, and certainly has no shortcoming as broad as suggested in the Summary line. Can you be more precise about "validating against an XSL file"? Are you talking about match= or select= path expressions? There is a well-known gotcha in match patterns, and the behavior would be the same for all conforming XSLT processors. Early Microsoft processors were not conformant in several ways, and this could be one. The "trick" described is in fact the standard way to make match patterns apply to elements or attributes that are in a specified namespace when that namespace is the default in the input document. In other words, <xsl:template match="foo"> is always for foo elements in *no* namespace, while <xsl:template match="myspace:foo"> is for elements whose namespace URI is the one corresponding to the "myspace" prefix in the stylesheet. In the input document, those foo elements could have the prefix "myspace", a different prefix, or no prefix (being in that namespace via declaration of a default namespace). Please clarify as requested above, or the bug can be deemed invalid.
