Scott, You're amazing. Thanks for all the help. I'll let you know if I find any bugs.
Chris Pittman eWorker Technologies -----Original Message----- From: Scott Nichol [mailto:[EMAIL PROTECTED]] Sent: Friday, August 30, 2002 6:42 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Apache Soap and MS Soap Chris, I've recently committed changes to allow you write Apache SOAP clients for document/literal services. You will need to get a nightly build (8/31 AM or later) or grab from the CVS tree. There is a doclit sample that works with a public doc/lit service. What you do is basically: 1. Map the de-serializers for the return values. This is necessary to handle the doc/lit response. It relies on the existing MS interop hack of supplying the element qname rather than the element type qname. 2. Code the call and parameters like soap/rpc encoding. 3. Do call.setDocLitSerialization(true) before invoking. My testing has been limited to the sample I wrote, so if you think you've come upon a bug, you may well have. Scott Nichol ----- Original Message ----- From: "Chris Pittman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 29, 2002 5:04 PM Subject: Re: Apache Soap and MS Soap Thanks for the info Scott. I'm pretty clueless about the Apache implementation. On a slightly different note, do you know if it is possible to run Apache SOAP on an IIS server? I haven't found anything that suggested it was possible but I'm hoping to avoid having to set up another web server like Tomcat to set it up. Thanks, Chris ---------- Original Message ---------------------------------- From: Scott Nichol <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Wed, 28 Aug 2002 17:13:38 -0400 >I'm not sure exactly what you mean, but if you are talking about leaving the >server doc/lit, the answer is no. The main problem is that Apache SOAP will >always send an encodingStyle attribute in the XML element for the method, >which will hose any MS server. > >The "workaround" published as an MSKB article requires tedious coding for >each method call. > >I think a doc/lit workaround will be added to Apache SOAP sometime within >the next couple of weeks, but I suppose you won't be able to wait that long >;-) > >Scott Nichol > >----- Original Message ----- >From: "Chris Pittman" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Wednesday, August 28, 2002 4:57 PM >Subject: RE: Apache Soap and MS Soap > > >Can I use the RPC style and just send an XML string as a parameter then? > > >Chris Pittman >eWorker Technologies > > >-----Original Message----- >From: Scott Nichol [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, August 28, 2002 4:23 PM >To: [EMAIL PROTECTED] >Subject: Re: Apache Soap and MS Soap > > >Apache SOAP does not do document/literal encoding today, without you writing >code to manually create and parse envelopes. > >Scott Nichol > >----- Original Message ----- >From: "Chris Pittman" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Wednesday, August 28, 2002 4:09 PM >Subject: Apache Soap and MS Soap > > >Hi, > >I'm trying to use an Apache Soap 2.3.1 client to connect to a web service >running on an IIS server with MS Soap. I'm using the document style. I >have written the server side and tested it using a MS client. However, I >don't know that much about setting up an Apache client. Can I use some of >the "standard" code snippets for implementing this, or will I need to be >creative because of the document style? > >Thanks, >Chris Pittman >eWorker Technologies -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
