Sorry, one clarification - Pull down the package 'Web Services Toolkit' from alphaWorks. "servicegen" is a utility bundled in the package.
Tony > -----Original Message----- > From: Tony Hong [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 25, 2002 5:12 AM > To: [EMAIL PROTECTED] > Subject: RE: Interop Problem .NET Client / Apache SOAP Server > > > Hi Martin, > > To generate Apache SOAP servers from WSDL defintions, try using > the IBM WSTK > utility "servicegen", available at http://www.ibm.com/alphaworks, > which will > create everything you need , including the deployment descriptor. You then > simply supply the implementation, and the server will then be strictly > conformant to the wsdl - no worrying about namespaces, soapaction, etc. > > Tony > > > -----Original Message----- > > From: Martin Centner [mailto:[EMAIL PROTECTED]] > > Sent: Friday, January 25, 2002 2:47 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Interop Problem .NET Client / Apache SOAP Server > > > > > > Simon Fell wrote: > > > > > Make sure your .NET proxy class thinks its doing section 5 encoding, > > > it sounds like its trying to do doc/literal. > > > > > > The method in the proxy class should have a > > > System.Web.Services.Protocols.SoapRpcMethodAttribute attribute on it. > > > > > > hm, this works fine with the HelloWorld expample, but if i want to > > return a more complex data structure i run into trubbles. > > > > The Apache SOAP RPC returns > > > > <SOAP-ENV:Envelope > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" > > xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" > > xmlns:xsd="http://www.w3.org/1999/XMLSchema"> > > <SOAP-ENV:Body> > > <ns1:GetTerminResponse xmlns:ns1="http://sicher.net/" > > SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> > > <return xsi:type="ns1:Termin"> > > <TerminID xsi:type="xsd:int">1</TerminID> > > <LV xsi:type="xsd:int">534766</LV> > > <Ort xsi:type="xsd:string">i7</Ort> > > <Zeit > xsi:type="xsd:timeInstant">1970-01-02T14:18:52Z</Zeit> > > <Pruefer xsi:type="xsd:int">2</Pruefer> > > </return> > > </ns1:GetTerminResponse> > > </SOAP-ENV:Body> > > </SOAP-ENV:Envelope> > > > > > > But the .NET wants to have it in this form (according to the WSDL) > > > > <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" > > xmlns:tns="http://sicher.net/" > > xmlns:types="http://sicher.net/encodedTypes" > > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > > <soap:Body > soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> > > <tns:GetTerminResponse> > > <GetTerminResult href="#id1" /> > > </tns:GetTerminResponse> > > <types:Termin id="id1" xsi:type="types:Termin"> > > <TerminID xsi:type="xsd:int">int</TerminID> > > <LV xsi:type="xsd:int">int</LV> > > <Ort xsi:type="xsd:string">string</Ort> > > <Zeit xsi:type="xsd:dateTime">dateTime</Zeit> > > <Pruefer xsi:type="xsd:int">int</Pruefer> > > </types:Termin> > > </soap:Body> > > </soap:Envelope> > > > > > > Im trying to get a .NET client to work with a .NET Webservice _and_ an > > Apache SOAP RPC service. > > > > cu > > lot > > > > > > > > > > > >