RE: Compatibility b/w SOAP and MS SOAP Toolkit

[Olivier Thomas <ol...@wanadoo.fr>]

Hi,

Your sample of code for buiding a MS SOAP Client to an Apache SOAP server is
very useful, thanks.

I have a problem on my server side to receive the parameter sent by the
client. My calling function is declared to reveceive an object of type
Element (org.w3c.dom.Element).

The content of the answer is:

"Error building response envelope at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:34
5)" and "java.lang.IllegalArgumentException: I only know how to serialize an
'org.w3c.dom.Element'. at
org.apache.soap.encoding.literalxml.XMLParameterSerializer.marshall(XMLParam
eterSerializer.java:114)".

DO you know where I can find a sample of code for the SOAP server dealing
with the request of an MS Client.

I am still using MS SOAP toolkit 1.0.

Thanks,
Olivier.

-----Original Message-----
From: Simpson, Jeff [mailto:jsimpson@ifinance.com]
Sent: mercredi 20 décembre 2000 11:18
To: Soap-User (E-mail)
Subject: Compatibility b/w SOAP and MS SOAP Toolkit


I notice a number of questions about this topic and here is how I get MS
Soap client to talk to an Apache Soap server.

Jeffrey V. Simpson
Senior Software Engineer
iFINANCE
Phone: 202.833.4949
Fax: 202.833.3819
URL: http://www.ifinance.com

-----Original Message-----
From: Simpson, Jeff
Sent: Monday, October 16, 2000 10:01 AM
To: 'soap-user@xml.apache.org'
Subject: RE: Compatibility b/w SOAP4J and MS SOAP Toolkit


Here is a snippet of Code that I use to get the MS side to talk to Apache.
It is not very Elegant but it works.  I don't use serializers in my work
since when I started my project, and IMHO still, looks like they can cause
some Incompatibility Issues.  So I use NS_URI_LITERAL_XML  this allows me to
get an Element and manipulate it as I will.  With the use of
NS_URI_LITERAL_XML you get to make up your XML yourself.  So My thinking is
that if you use ApacheSoap as the Client you may want to use
NS_URI_LITERAL_XML to build the call.