axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24845] - [doc/lit] complexType in SOAP response has namespace prefix, chokes .net clients
Date Mon, 24 Nov 2003 23:18:53 GMT
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=24845>.
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=24845

[doc/lit] complexType in SOAP response has namespace prefix, chokes .net clients





------- Additional Comments From lycono@mindless.com  2003-11-24 23:18 -------
I've done a little poking around the Axis serialization code looking to see if
this was something that we could fix locally for the time being.  Turns out that
may not be the case.  We use the Axis BeanSerializer for all types defined by
schemas.  The BeanSerializer uses the SimpleSerializer to write out values.  The
SimpleSerializer in turn uses the "startElement" method in
SerializationContextImpl to write start tags to the stream.  Lines 917-920 in
SerializationContextImpl.java are 

BEGIN CODE:

String elementQName = qName2String(qName, true);
writer.write('<');

writer.write(elementQName);

:END CODE

That hardcoded "true" argument in the call to qName2String forces the namespace
prefix to be included in the returned value.  There doesn't seem to be any
contextual information that would be able to indicate whether or not a prefix
should be attached to a particular element.

Mime
View raw message