DO NOT REPLY [Bug 17746] - xmlns="" appened to subsequent element when no namepsace prefix

[bu...@apache.org]

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=17746>.
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=17746

xmlns="" appened to subsequent element when no namepsace prefix

adam_craven@technologyonecorp.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Critical
           Priority|Other                       |Medium
   Target Milestone|---                         |1.1 Final



------- Additional Comments From adam_craven@technologyonecorp.com  2003-04-11 18:28 -------
I have noticed some similar behaviour when a javabean is serialised as the 
response to a service call. I am using the document/literal encoding in the 
wsdl, and in the wsdd: provider="java:rpc" style="wrapped" use="literal".

The response message returned to the dot net client is:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd=...>
 <soapenv:Body>
  <MethodResponse xmlns="http://example.com/service">
   <return xmlns="">
    <...>

This causes big problems with dot net as it won't instantiate a return object 
because of the invalid/unknown namespace.

I would think that this type of issue should be fixed for the final 1.1 
release. 

I don't know how I can do a workaround, since the bean serialiser is doing all 
the work for me - unlike Darren who is manually coding the soap envelope...