JAX-WS is just one API; Axis2 implements a good deal more, e.g. WS-Security. The built-in stuff also limits you to using the built-in web server (which is rather limited in capability), and the API versions it implements (of JAX-WS and JAXB) are already outdated. So I wouldn't use it for more than toying around; certainly not for a production setting.
Ping & DNS - updated with new look and Ping home screen widget
Joined: Sep 25, 2008
Thanks. What about this comparison? Did they compare the built in jax-ws or the axis2 jax-ws?
If I do decide to use the implementation of axis2 is the config the same? I mean web.xml: <servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class> ..... <listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
Did they compare the built in jax-ws or the axis2 jax-ws?
Looks like he compared the RI with the Axis2 implementation. The JDK6 version is an older version of the RI.
If I do decide to use the implementation of axis2 is the config the same?
No, the details are not the same - they're different implementations. In particular, no changes to the Axis 2 web.xml are necessary. Axis2 comes with a number of examples that show how to use various aspects of JAX-WS in use.