Sun says their RI is production-ready: http://java.sun.com/xml/jaxrpc/overview.html: Sun provides a product-quality reference implementation of JAX-RPC that is bundled as part of the Java Web Services Developer Pack (Java WSDP). This reference implementation will also be available as part of the J2EE platform reference implementation.
Java.net, which hosts the source project, says this: https://jax-rpc.dev.java.net/: The goal of the JAX-RPC project is to provide the Reference Implementation of JAX-RPC, the Java APIs for XML based RPC. The JAX-RPC specification is developed through the Java Community Process following the process described at jcp.org. This process involves an Expert Group with a lead that is responsible for delivering the specification, a reference implementation (RI) and a test compatibility kit (TCK). The primary goal of an RI is to support the development of the specification and to validate it. Specific RIs can have additional goals; the JAX-RPC RI is a production-quality implementation that is used directly in a number of products by Sun and other vendors. To emphasize the quality of the implementation we sometimes call it a Standard Implementation. > -----Original Message----- > From: Wagle, Shriniwas [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 30, 2004 9:50 AM > To: [EMAIL PROTECTED] > Subject: RE: Axis vs JWSDP 1.4 > > JWSDP is Sun's reference implementation of the APIs. I'm sure you'd > find more detailed definition on what a "reference > implementation" means > on Sun's site, but in short it's like a proof of concept for the APIs > being implemented. So it's not production quality material. For > instance, could potentially run into performance issues. > > -----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 > >
