Gary, had the same problem in the past, you could check at http://mail-archives.apache.org/mod_mbox/ws-axis-user/200503.mbox/thread s.html the thread "is it possible to change soapenc:string to xsd:string in generated WSDL?"
cu Merten > -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 19, 2005 4:39 PM > To: [email protected] > Subject: Re: Issue with .NET client consuming a AXIS WS > > .NET has a problem consuming soapencoding:string types. > > Change this: > <wsdl:message name="processOrderResponse"> > <wsdl:part name="processOrderReturn" type="soapenc:string"/> > </wsdl:message> > > To this: > <wsdl:message name="processOrderResponse"> > <wsdl:part name="processOrderReturn" type="xsd:string"/> > </wsdl:message> > > Anne > > On 7/13/05, Gary Zhu <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > I deployed a WS on AXIS and was able to consume it through > AXIS client. > > However, .NET client seems to be having problems consuming > the AXIS web > > service and is getting a timeout error. Your help is appreciated. > > > > Attached is the WSDL for the WS, and WSDD file. > > > > Thanks in advance. > > > > Gary > > >
