Not sure if the comparison JAX-RPC comparison with Struts
is exactly accurate. Switching between JWSDP and Axis is a matter of
switching JAX-RPC providers with no change to application
code.
Struts vs "No Struts" means you are now writing
new application code to do what Struts would do for you out of the
box.
And yes, you are right
when you say that with Axis you are get the "Axis framework" too which you can
work with and extend.
I feel that a lot of applications could get by
with using JAX-RPC, without tying into a specific
provider.
From: Kim Tan [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 30, 2004 11:20 AM
To: [EMAIL PROTECTED]
Subject: RE: Axis vs JWSDP 1.4
The way I see is that when you use Axis,you are buying into the "Axis
webservice framework" of building web services, and if you use the JWSDP, you
are basically just using the API, which Axis supports and extends.
It is kind of similar to those using Struts for MVC type of application
framework, you can do the same with straight JAVA,but Struts provide you will
some convenient method to build the MVC apps.
So it is kind of boiling down to whether you feel comfortable with Axis or
just pure JAVA....
Derek Richardson <[EMAIL PROTECTED]> wrote:
> -----Original Message-----
> From: Derek Richardson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 30, 2004 12:21 AM
> To: [EMAIL PROTECTED]
> Subject: Axis vs JWSDP 1.4
>
> I'm starting a web services project and am hoping that either Axis or
> Sun's Java Web Services Developer Pack will fulfill our needs for
> exposing and consuming web services.
>
> I know that those who have already invested in implementations using
> Axis have a reason to continue using it. My question is: for a new
> project, why should I choose Axis over the JWSDP? Or vice versa.
>
> Thanks,
>
> Derek Richardson
>
>
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
