Hi Brian,
Thanks for the link. I looked it over and it looks like it would work with Axis on the server side even though it supports a subset of SOAP 1.1.
Is that a correct interpretation? What I am looking for is for a client side implementation where I can still use Axis SOAP server (I am very happy with Axis server side servlet and do not want to change that). Also, I am passing a message object on the client side into the Axis API so I do not have to have to do a lot of work (coding) on the client side.
Many Thanks,
Tony
-----Original Message-----
From: Brian Ewins [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 21, 2003 10:12 AM
To: [EMAIL PROTECTED]
Subject: Re: Axis Client Performance issue explained
Anecito, Anthony (HQP) wrote:
[..."I am using applets, wireless"...]
> 1. Only use stand-alone clients
> 2. Use perhaps Sun JAXP (very small jars <20K compared to 3MB> for axis
> jars)
> 3. Drop Axis all together (great concept if you can live with
> stand-alone and non-light clients)
>
> Any Ideas?
Use kSOAP. Its intended for applets. Axis isn't.
A comparison between kSoap and Axis:
- axis is based on the JAX* apis, so you can swap in different parsers,
etc.
- kSOAP is designed to run on top of XMLPULL parsers, but is not
pluggable in any other way.
- axis is aimed at J2SE
- kSOAP is aimed at J2ME (ie /wireless devices/)
- axis supports all of SOAP 1.1 (and bits of 1.2), plus SwA, DIME.
- kSOAP supports a subset of SOAP 1.1.
- axis supports code generation from WSDL.
- kSOAP doesnt. (NB its probably possible to adapt axis' wsdl2java to
generate code for kSOAP, or achieve good-enough results with some XSL)
In other words: axis provides flexibility at a price.
-Baz
