Re: InterOp. between Java Client and .NET Web Service and vice versa

2002-09-26 Thread Scott Nichol
AIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 26, 2002 6:04 AM Subject: Re: InterOp. between Java Client and .NET Web Service and vice versa > Thanks so much for yours helping. > The VB Client works well :-) > And about Java Client Code> I realized that the

Re: InterOp. between Java Client and .NET Web Service and vice versa

2002-09-26 Thread penguin
Thanks so much for yours helping. The VB Client works well :-) And about Java Client Code> I realized that the doclit example is as same as my Java Client Code, except the line: call.setDocLitSerialization(true); What is it used for ? P/s: I cannot run the doclit example, it tells that: "Caught S

Re: InterOp. between Java Client and .NET Web Service and vice versa

2002-09-25 Thread Scott Nichol
Java client and .NET Web service If you look at your WSDL, you will see that it specifies "literal" encoding. Apache SOAP by default uses "encoded" encoding. Your service is ignoring the parameter that is sent to it because that parameter has an xsi:type attribute

RE: InterOp. between Java Client and .NET Web Service and vice versa

2002-09-25 Thread Jean-Louis Vila
Hi, First : Java client -> .NET In .NET, your WS is wrote in document Style Your Java client usr RPC style !!! So if you use same SOAP style invocation, all will work fine. To see if the SOAP message is ok, you can use the wonderful tool : TCPMon