All geek questions in one place

Axis2 vs JAX-WS

I need to implement SOAP-based web services for a project. We are considering various options, such as axis2, ejb as a web service, jax-ws, but are not quite sure about the advantages / disadvantages of these options. Someone can help in this regard.

It would be great if someone could point out any other alternatives for implementing SOAP-based web services.

Thanks in advance, -CSN

+4
source share
2 answers

I highly recommend using Apache CXF to develop SOAP web services. This stack is based on JAX-WS , but has much more features. CXF has excellent integration with Spring . There is a lot of documentation on the Internet on how to create web services using this infrastructure. If I were working on a completely new web service, I would choose Apache CXF .

+2
source

For me, the easiest way to open a web service is to create an EJB with annotations (JAX-WS) if you are using a Java EE server, such as JBoss.

WS consumption is a little different, but I prefer JAX-WS because Axis2 throws exceptions if you use complex parameters (classes) and add an attribute. JAX-WS instead calls each "get" and "set" for serialized xml. If "set" is not implemented, there is no problem. This is an advantage for backward compatibility.

+4
source

Source: https://habr.com/ru/post/1437193/

More articles:


All Articles