DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28220>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28220 Fatal Error:The prefix "xmlns" cannot be bound to any namespace explicitly ------- Additional Comments From [EMAIL PROTECTED] 2004-04-08 01:20 ------- The answer to 1) is that the namespace declaration in this start tag: <name xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace"> is allowed. It's just not required to be declared because this namespace binding exists by definition. The text you are quoting from the spec disallows namespace declarations of the following form: <name xmlns:xmlns="http://www.w3.org/2000/xmlns/"> <name xmlns:xmlns="http://www.something.com/"> <name xmlns:prefix="http://www.w3.org/2000/xmlns/"> None of these are in the example you've given. The answer to 2) is that the binding between the prefix 'xml' and the namespace 'http://www.w3.org/XML/1998/namespace' exist without being explicitly declared. Any qualified name prefixed with xml is in this namespace, such as xml:lang. Any parser which conforms to the spec will report this as the namespace URI. If you look at the traces the parser (at least the version in CVS) is neither reporting a namespace mapping for the xml prefix, nor is it reporting an attribute named 'xmlns:xml'. My best guess is that this attribute is being inserted by Axis after the parser reports SAX events to it. Wherever it's coming from this declaration is not illegal. It sounds like the result returned from Axis' deserialization context: <soap-env:Envelope xmlns:soap- env="http:schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><find_business generic="2.0" xmlns="urn:uddi-org:api_v2"><name xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace">abc</name></find_business></soa p-env:Body></soap-env:Envelope> is being sent to another application. This document does not attempt to bind xmlns to its namespace, or the xmlns namespace to another prefix. Is this document processed by some other application? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
