AXIS vs JAX-WS for Web Service Client

java soap wsdl jax-ws axis
jny picture jny · Jan 7, 2011 · Viewed 10.9k times · Source

I am deciding on the implementation of Web Service Client in Java. I've generated Axis client in Eclipse and JAS-WS client with wsimport. Both solutions work and now I have to choose one to go forward. What should I think about before picking one over the other?

Answer

jarnbjo picture jarnbjo · Jan 7, 2011

The client side of JAX-WS is part of the standard Java API, and the reference implementation is reliable and performant, while Axis requires 3rd party dependencies. If you don't need any functionality implemented by Axis and not offered by JAX-WS, I really don't see any reason why you should opt for Axis and not for JAX-WS.

Related questions

Java SOAP "wsimport" - force wrapped binding from document/literal wrapped WSDL?

The Java 6 JAX-WS "wsimport" utility does a great job of generating a web service skeleton (interface) given a WSDL file but with one personally annoying exception. When given a WSDL that uses the SOAP Document/literal wrapped style (also described …

Read More
How to call a SOAP web service on Android

I am having a lot of trouble finding good information on how to call a standard SOAP/WSDL web service with Android. All I've been able to find are either very convoluted documents and references to "kSoap2" and then some …

Read More
Difference between a SOAP message and a WSDL?

I am confused about how SOAP messages and WSDL fit together? I have started looking into SOAP messages such as: POST /InStock HTTP/1.1 Host: www.example.org Content-Type: application/soap+xml; charset=utf-8 Content-Length: nnn <?xml version="1.0"?> <…

Read More