|
Sounds like an artifact of our Array serializer
work that was unintended. The type from the WSDL doesn’t match the type
of the element in the array. Does the WSLD say xsd:anyType? The more we fix arrays, the more bugs we
seem to generate. L Tom Jordahl From: Jim Cross
[mailto:[EMAIL PROTECTED] I'm
assessing a server from the client side. I'm not sure what the server is
written with. I've tried this with 1.1, 1.2, and 1.2.1. The
generated proxies have this statement before the service request.
_call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR, Boolean.FALSE);
I
can also confirm that MessageContext
property name=sendXsiTypes value=false Nevertheless,
with a particular string array, the client insists on generating xsi:type="xsd:string"
on the element Removing
the xsi:type and sending the SOAP XML via a raw post to the server works, so it
is definite that this is problem. As
far as I tell from some limited debugging, the code gets deep into its
serialization and compares the xmlType with an actualType (not sure where or
how this is created or what purpose it serves). If these are different, it
seems to generate the xsi:type no matter what the property setting is. Any
idea how to work around this? |
Title: Client insists on sending xsi type
- RE: Client insists on sending xsi type Tom Jordahl
- RE: Client insists on sending xsi type Jim Cross
- Re: Client insists on sending xsi type Anne Thomas Manes
