Spring-ws VS Apache cxf VS Apache Axis2 VS Metro

Question

I need to create soap web service. I already have wsdl and interface and implementation (as pojo).

I am now choosing between subj. I need frame work that will:

• Work as servlet in servlet container
• Require only one servlet mapping in my web.xml
• Have good spring integration (because my service implementation is spring bean)

• No require me to add annotations. I do not have annotations on my interface or implementation.

• Spring-ws: Looks cool, but as far as I understood it forces me to deal with XML directly which I do not want to do. I want framework to deserialize message and pass it as parameter to my POJO.

• Apache cxf is powerful and has spring integration, but if I use Jax-WS frontend for it I will have to use annotations, and I do not want to touch my POJO. What about simple front-end?

• Metro is Jax-WS RI, so it depends on annotations heavily.

Axis2 seems to be my choice. What would you choose?

---

Just wanna tell what I am trying to do: Our app connects to remote service using SOAP. They gave us WSDL, we've generated proxy classes and DTO and all this stuff is packed in jar and stored in VCS. Now I need to write emulation for this web service. And I do not want to generate new DTO.

Answer 1

I think Spring WS would be a good fit for you given your requirements. You do not need to deal directly with the XML. Spring will serialize/deserialize many types of objects including all of your data transfer objects. They should just be annotated JAXB entities. Check out this information: http://static.springsource.org/spring-ws/sites/2.0/reference/html/server.html#d5e1063

If you already have a WSDL you can generate your DTO objects from that WSDL. There are several tools that do this including most IDE's.