You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Andrew Fawcett <An...@coda.com> on 2002/04/10 10:48:59 UTC

RE: Connecting to .NET Document style web service with Apache SOA P 2.2

A few months ago I had some success with a .NET client and a Apache SOAP 2.2
Web Service using the 'literal' encoding style. I used Castor and the .NET
XML Serializer to serialize/marshall the XML in the envolope into
pre-generated objects (from a shared WSDL) at each end. If you want some
more details/sample code on this just let me know. Cheers.

-----Original Message-----
From: Oren Bar-El [mailto:Oren.Bar-el@smarteam.com]
Sent: 10 April 2002 09:28
To: soap-user@xml.apache.org
Subject: Connecting to .NET Document style web service with Apache SOAP 2.2



Hi All,

I am looking for the best way to connect to .NET Document style web service
using the Apache SOAP 2.2.

I tried doing it while staying out of the Apache code, but it seemed
impossible, since the Apache code contains hard coded elements (like
encodingStyle attribute, and namespace declarations) that prevent .NET from
reading parameters.

Finally, I decided to copy several classes from the Apache SOAP into my
project (AttributeHandler, Body, Call, Envelope, Response, RPCMessage,
SOAPHTTPConnection, SOAPTransport), and make the necessary changes. 

The only class I actually touched was the RPCMessage (marshall method), but
I needed all the rest of them to get there...

After making the mentioned changes to RPCMessage, and creating and mapping a
customized class to every method response, my client was able to access the
.NET document style service (with .NET default Document style behaviour).

Note that except for the outgoing SOAP message (generated by the altered
RPCMessage), the Apache SOAP still uses within itself the SOAP Encoding (for
type mappings ect.).

I do not like this solution too much, but it is the easiest way I could
find, and it actually works...

I also know that Apache's next SOAP version (Axis), which is at beta1 stage,
has much better support for this, but I can't afford to wait for Axis
release.

I was wondering if anybody has a better (or nicer) way to do this or just
comment about this.

Thanks,

Oren.

Re: Connecting to .NET Document style web service with Apache SOAP 2.2

Posted by "David B. Bitton" <da...@codenoevil.com>.
Connecting to .NET Document style web service with Apache SOAP 2.2I would be _very_ interested in seeing both ends.  Currently i am sending "literalxml" from MS SOAP Toolkit 2.0 to an Apache SOAP method, and it works well.  We will be going to .NET soon, and I'd like to make to migration as painless as possible.  Thanks.
--

David B. Bitton
david@codenoevil.com
www.codenoevil.com

Code Made Fresh DailyT
  ----- Original Message ----- 
  From: Andrew Fawcett 
  To: 'soap-user@xml.apache.org' 
  Sent: Wednesday, April 10, 2002 4:48 AM
  Subject: RE: Connecting to .NET Document style web service with Apache SOAP 2.2


  A few months ago I had some success with a .NET client and a Apache SOAP 2.2 Web Service using the 'literal' encoding style. I used Castor and the .NET XML Serializer to serialize/marshall the XML in the envolope into pre-generated objects (from a shared WSDL) at each end. If you want some more details/sample code on this just let me know. Cheers.
    -----Original Message-----
    From: Oren Bar-El [mailto:Oren.Bar-el@smarteam.com]
    Sent: 10 April 2002 09:28
    To: soap-user@xml.apache.org
    Subject: Connecting to .NET Document style web service with Apache SOAP 2.2


    Hi All,

    I am looking for the best way to connect to .NET Document style web service using the Apache SOAP 2.2.

    I tried doing it while staying out of the Apache code, but it seemed impossible, since the Apache code contains hard coded elements (like encodingStyle attribute, and namespace declarations) that prevent .NET from reading parameters.

    Finally, I decided to copy several classes from the Apache SOAP into my project (AttributeHandler, Body, Call, Envelope, Response, RPCMessage, SOAPHTTPConnection, SOAPTransport), and make the necessary changes. 

    The only class I actually touched was the RPCMessage (marshall method), but I needed all the rest of them to get there...

    After making the mentioned changes to RPCMessage, and creating and mapping a customized class to every method response, my client was able to access the .NET document style service (with .NET default Document style behaviour).

    Note that except for the outgoing SOAP message (generated by the altered RPCMessage), the Apache SOAP still uses within itself the SOAP Encoding (for type mappings ect.).

    I do not like this solution too much, but it is the easiest way I could find, and it actually works...

    I also know that Apache's next SOAP version (Axis), which is at beta1 stage, has much better support for this, but I can't afford to wait for Axis release.

    I was wondering if anybody has a better (or nicer) way to do this or just comment about this.

    Thanks,

    Oren.

Re: Connecting to .NET Document style web service with Apache SOAP 2.2

Posted by "David B. Bitton" <da...@codenoevil.com>.
Connecting to .NET Document style web service with Apache SOAP 2.2I would be _very_ interested in seeing both ends.  Currently i am sending "literalxml" from MS SOAP Toolkit 2.0 to an Apache SOAP method, and it works well.  We will be going to .NET soon, and I'd like to make to migration as painless as possible.  Thanks.
--

David B. Bitton
david@codenoevil.com
www.codenoevil.com

Code Made Fresh DailyT
  ----- Original Message ----- 
  From: Andrew Fawcett 
  To: 'soap-user@xml.apache.org' 
  Sent: Wednesday, April 10, 2002 4:48 AM
  Subject: RE: Connecting to .NET Document style web service with Apache SOAP 2.2


  A few months ago I had some success with a .NET client and a Apache SOAP 2.2 Web Service using the 'literal' encoding style. I used Castor and the .NET XML Serializer to serialize/marshall the XML in the envolope into pre-generated objects (from a shared WSDL) at each end. If you want some more details/sample code on this just let me know. Cheers.
    -----Original Message-----
    From: Oren Bar-El [mailto:Oren.Bar-el@smarteam.com]
    Sent: 10 April 2002 09:28
    To: soap-user@xml.apache.org
    Subject: Connecting to .NET Document style web service with Apache SOAP 2.2


    Hi All,

    I am looking for the best way to connect to .NET Document style web service using the Apache SOAP 2.2.

    I tried doing it while staying out of the Apache code, but it seemed impossible, since the Apache code contains hard coded elements (like encodingStyle attribute, and namespace declarations) that prevent .NET from reading parameters.

    Finally, I decided to copy several classes from the Apache SOAP into my project (AttributeHandler, Body, Call, Envelope, Response, RPCMessage, SOAPHTTPConnection, SOAPTransport), and make the necessary changes. 

    The only class I actually touched was the RPCMessage (marshall method), but I needed all the rest of them to get there...

    After making the mentioned changes to RPCMessage, and creating and mapping a customized class to every method response, my client was able to access the .NET document style service (with .NET default Document style behaviour).

    Note that except for the outgoing SOAP message (generated by the altered RPCMessage), the Apache SOAP still uses within itself the SOAP Encoding (for type mappings ect.).

    I do not like this solution too much, but it is the easiest way I could find, and it actually works...

    I also know that Apache's next SOAP version (Axis), which is at beta1 stage, has much better support for this, but I can't afford to wait for Axis release.

    I was wondering if anybody has a better (or nicer) way to do this or just comment about this.

    Thanks,

    Oren.