RE: [jira] Commented: (AXIS2-249) Exessive number & size of filesgenerated from WSDL

[Sanjiva Weerawarana <sa...@opensource.lk>]

On Sun, 2005-10-02 at 11:18 -0700, Simon Fell wrote:
> If that's the price for using XMLBeans data binding, what's the
> benifit ?

Alek already answered this.
> 
> The vast majority of the users want to use a strongly typed object
> model generated from the WSDL, most of the don't care (and nor should
> they) about xml, soap and the general intrictisy of web services. Most
> of them would be even happier if we stopped shipping WSDLs and shipped
> a taylor made client api instead. (even if that used SOAP under the
> covers).
> 
Understood. I wasn't arguing that you should change what you are doing;
I was asking whether an XML centric solution would work. In any case, I
agree a JAX{B,RPC,WS} compliant data binder is a requirement for Axis2.

> I asked this question to the Indigo folks, so i ask here too, SForce
> is a WSI BP compliant service, Axis 1.x already handles it, why should
> i move my client code from Axis 1.x to Axis 2.x ?

WSI-BP only deals with simple stuff. If that's all that's necessary I
agree that Axis2 won't give you a hell of a lot over and above Axis1. 

Looking down the road, do you want to support SForce over something like
email? If so you need addressing; then Axis2 adds something for you.
Basically if you do any async or doc/lit stuff, then Axis2 is designed
to better fit those needs than Axis1 is. Maybe over time you'll need to
offer WS-RM support for SForce- then you'll be much better off with
Axis2 as the base. 

I don't believe *every* Axis1 user will switch to Axis2; hell there are
*lots and lots* of people who still use Apache SOAP in production (and
quite happily too). I, of course, would like if everyone would jump ship
to Axis2 but that's not realistic to expect because Axis1 and Apache
SOAP are both damned good products for what they do and there will be
people who will not change unless the new beast scratches an itch.

Sanjiva.