RE: Axis vs JWSDP 1.4

[Anne Thomas Manes]

I disagree. The Sun JAX-RPC reference implementation in JWSDP contains a web services framework that’s comparable to (albeit different from) the framework in Apache Axis. The point is that someone that implements the JAX-RPC API can’t simply implement the API – they also must supply a SOAP/WSDL runtime framework.   I think that Axis is easier to use than JWSDP, though.   Anne   From: Kim Tan [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 5:20 PM 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!