Axis Client Performance issue explained

["Anecito, Anthony (HQP)" <To...@rhi.com>]

Hi All,

Many thanks to Mike Burati for helping out. A stand-alone application using
Axis will perform admirably but a dynamic (mobile) agent such as an applet
does poorly due to the fact the Axis Jars are quite big. It is further
aggravated if one is using wireless technology and encryption is added on
top of that. Delays over 50 seconds for each call object creation or invoke
operation can occur. This is because the call can occur while code is being
downloaded to the browser. I have arrived at some possible solutions and
please let me know if anyone has any thoughts about this.

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?
Thanks,
Tony

RE: Axis Client Performance issue explained

[Anne Thomas Manes <an...@manes.net>]

Another option is Wingfoot SOAP (www.wingfoot.com).
It's another J2ME-based SOAP implementation.
(free, but not open source)

Anne

> -----Original Message-----
> From: Brian Ewins [mailto:Brian.Ewins@btinternet.com]
> Sent: Friday, February 21, 2003 1:12 PM
> To: axis-user@ws.apache.org
> 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.
>
> http://www.ksoap.org/
>
> 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
>
>

Re: Axis Client Performance issue explained

[Brian Ewins <Br...@btinternet.com>]

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.

http://www.ksoap.org/

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