I ran into this yesterday. Basically it is a bug in MS but you can work around it by adding fake marshalling info to your Apache deployment descriptor. see:
http://marc.theaimsgroup.com/?l=soap-dev&m=97901982213396&w=2
Attached is my deployment descriptor as an example. you might also want to see:
http://marc.theaimsgroup.com/?l=soap-dev&m=98709541430159&w=2
This is your next problem (Content-Type=text/xml; charset=utf-8). I have not resolved this yet so if you have any clues, or don't run into it, please let me know what your configuration is.
Hope this helps.
Robert Larson
Sr Architect
Saba
www.saba.com
+1 (650) 581-2559
<isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" id="urn:hcdm-content-core">
<isd:provider type="java"
scope="Application"
methods="listInitialValues authenticate">
<isd:java class="com.saba.content.core.soap.CIFCoreService" static="false"/>
</isd:provider>
<isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
<isd:mappings>
<isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:cif="urn:hcdm-content-core" qname="cif:Core"
javaType="com.saba.content.core.CIFCoreBean"
java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer"
xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/>
<isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:cif="urn:hcdm-content-core" qname="cif:LocaleBean"
javaType="com.saba.content.common.SabaLocaleBean"
java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer"
xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/>
<isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:cif="urn:hcdm-content-core" qname="cif:ContentServerBean"
javaType="com.saba.content.common.ContentServerBean"
java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer"
xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/>
<!-- MS SOAP Toolkit 2.0 does not correctly add type information to the Parts
when the soap:body is specified to use="encoded". The following mappings
are workarounds to let the Apache SOAP marshalling work correctly -->
<isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:x="" qname="x:username"
javaType="java.lang.String"
xml2JavaClassName="org.apache.soap.encoding.soapenc.StringDeserializer"/>
<isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:x="" qname="x:password"
javaType="java.lang.String"
xml2JavaClassName="org.apache.soap.encoding.soapenc.StringDeserializer"/>
</isd:mappings>
</isd:service>
-----Original Message-----
From: Sheeba Padmanabhan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 27, 2001 7:42 AM
To: [EMAIL PROTECTED]
Subject: MS soap client communicatig to Apache Soap xsi:type error
Hi,
I have a MS C++ Soap client communicating to Apache soap server using WSDL.
But when I pass string as arguments to the service method, its failing due
to the absence of xsi:type in MS soap. Any idea about how to set the soap
attribute for "xsi:type", "xsd:string" ?
Any help would be highly appreciated.
Thanks
Sheeba
