Return-Path: <gaetan@frenoy.net>
Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list axis-user@xml.apache.org
Received: (qmail 88043 invoked from network); 7 May 2002 11:05:28 -0000
Received: from vic.be.wanadoo.com (HELO wanadoo.be) (195.74.212.103)
  by daedalus.apache.org with SMTP; 7 May 2002 11:05:28 -0000
Received: from localhost.localdomain (adsl-128-40.wanadoo.be [213.177.128.40])
	by wanadoo.be (8.12.2/8.12.2) with ESMTP id g47B50A22558364
	for <axis-user@xml.apache.org>; Tue, 7 May 2002 13:05:00 +0200 (MEST)
Received: from frenoyg1.frenoy.net ([192.168.1.2])
	by localhost.localdomain (8.12.1/8.12.1) with ESMTP id g47B7GKQ005563
	for <axis-user@xml.apache.org>; Tue, 7 May 2002 13:07:16 +0200
Message-Id: <5.1.0.14.2.20020507130156.0280b080@frenoy.homeip.net>
X-Sender: gaetan@frenoy.homeip.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 07 May 2002 13:05:41 +0200
To: axis-user@xml.apache.org
From: Gaetan Frenoy <gaetan@frenoy.net>
Subject: Re: Compatibility with Microsoft toolkit
In-Reply-To: <5.1.0.14.2.20020507083936.02805860@frenoy.homeip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-DCC-wanadoo-be-Metrics: vic.be.wanadoo.com 1016; IP=0 env_From=0 From=0
	Message-ID=0 Received=0 Body=1 Fuz1=1 Fuz2=1
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hello,

On http://www.intranetjournal.com/articles/200103/id_03_21_01b.html,
I found this:

"The Apache system requires all the arguments to be typed
using the xsi:type attribute, while the Microsoft system
does not require this. The next version of Apache SOAP (2.1)
should be able to guarantee interoperability between these
two implementations. "

It answers some of my questions but now, I got more:
  - They're talking about Apache SOAP 2.1, does Axis will
    guarantee that interoperability ?
  - If yes, when?

Thanks.


At 09:14 5/7/02 +0200, you wrote:
>Hi all,
>
>After installing Axis beta 2 and Tomcat 3.3.1 on my NT box,
>I could successfully run your samples - e.g. Calculator:
>
>   java samples.userguide.example2.CalcClient -p8080 add 5 8
>   Got result : 13
>
>This looks like a great job!
>
>
>Now, I was trying to call the Calculator sample from some
>Visual Basic code using MS SOAP Toolkit 2.0 :
>
>  Call=
 soapclient.mssoapinit("http://localhost:8080/axis/Calculator.jws?wsdl")
>  wscript.echo soapclient.add(1, 2)
>
>It looks to call the service properly...Unfortunately, it failed returning
>the following error:
>
>  java.lang.IllegalArgumentException: argument type mismatch
>
>
>By examining the exchanged messages with tcpdump, I can see the following
>
>1) When call from an Axis client:
>----
>POST /axis/Calculator.jws HTTP/1.0
>Content-Length: 485
>Host: localhost
>Content-Type: text/xml; charset=3Dutf-8
>SOAPAction: ""
>
><?xml version=3D"1.0" encoding=3D"UTF-8"?>
><SOAP-ENV:Envelope=20
>SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/"=20
>xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"=20
>xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"=20
>xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"=20
>xmlns:SOAP-ENC=3D"http://schemas.xmlsoap.org/soap/encoding/">
>  <SOAP-ENV:Body>
>   <add>
>    <op1 xsi:type=3D"xsd:int">5</op1>
>    <op2 xsi:type=3D"xsd:int">8</op2>
>   </add>
>  </SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>----
>
>2) When called from MS SOAP Toolkit client:
>----
>POST /axis/Calculator.jws HTTP/1.1
>Content-Type: text/xml; charset=3D"UTF-8"
>Host: localhost
>SOAPAction: ""
>Content-Length: 320
>
><?xml version=3D"1.0" encoding=3D"UTF-8"=
 standalone=3D"no"?><SOAP-ENV:Envelope=20
>SOAP-ENV:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/"=20
>xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body=
><SOAPSDK1:add=20
>xmlns:SOAPSDK1=3D"add"><i1>1</i1><i2>2</i2></SOAPSDK1:add></SOAP-ENV:Body><=
/SOAP-ENV:Envelope>
>----
>
>So my questions:
>  - Is it supposed to fail?  I mean, isn't SOAP supposed to be independant
>    of the implementation?
>  - Why is that failing exactly?
>  - Is this a general compatibility problem?  Note that this would be
>    a showstopper for our project.
>  - Is there an easy workaround transparent from the client-side?
>
>
>Many thanks for your help.
>
>
>--
>Ga=EBtan Frenoy (aka Gaff)
>gaetan@frenoy.net
>Brussels - Belgium

--
G