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 9927] - ElementSerializer adds unnecessary xsi:type attribute
Date Mon, 17 Jun 2002 20:38:01 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=9927>.
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=9927

ElementSerializer adds unnecessary xsi:type attribute

wollsch@us.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From wollsch@us.ibm.com  2002-06-17 20:38 -------
Maybe I didn't describe my problem good enough:

If I'm going to describe my message in WSDL/XSD, I may already define a type for this. When
axis specifies a "http://xml.apache.org/xml-soap:Element" in the element serializer then this
might be inconsistent with the WSDL and the message will nott validate. 

The ElementSerializer probably shouldn't specify xsi:type in any case, even if the AxisEngine.PROP_SEND_XSI
is set to true.

But in some cases (e.g. XMLSchema primitives) I guess it's OK to use the xsi:type. 

Maybe axis could add method(s) to specify programatically specify the xsi on the RPCElement/RPCParam
and so on. The the serializer should either use this or if it cannot infer the correct type
it wouldn't specify the attribute.

I'm sorry I don't know how to fully specify this, but the current behaviour is a bug! :-)

Mime
View raw message