Which web services framework to choose

[Jean-Marc Bottin]

Hi all,

I was wondering which framework are you using for developing and consuming web services.

I am a little bit confused because I don't know which framework to use:
Apache Axis2
Apache CXF
Xfire codehaus
Spring WS
and others...

Based on your experiences what do you suggest?

Regards
Jean-marc

[Ulf Dittmer]

I've been using (and been happy with) Axis 2 for a long time. Mostly because when I started working with WS in Java, there was only Apache SOAP, from where the road led to Axis 1 and now to Axis 2.

It supports just those standards/protocols I care about (SOAP, WSDL, WS-Security, SAAJ, JAX-WS), and few others, so there isn't a lot of unneeded baggage.

If I were starting out today I'd also look into the Metro stack (which comes with all the bells and whistles), mostly because it seems to evolve by leaps and bounds. Granted, most of those features I might not use, but it'd be interesting nonetheless.

[Nitin Gaur]

Choice is yours, it makes sense to use :
1) JBossWS native - if you're already using JBoss AS
2) SpringWS - if you're already using Spring framework
3) Apache CXF - if you want an easy to use toolkit that provides pure web services nothing else.
4) GlassFish Metro - if you want to go with JAX-WS reference implementation promoted by Sun itself.
5) Axis2 - For any other case

HTH
-Nitin Gaur

[Jair Rillo Junior]

I have been using Apache AXIS 2, which comes by default in IBM Websphere 6.1, and I had no problem so far, by the way, it is easy to work with.

Also, I agree with Nitin. Depends on which APP Server you're using, choose its default Web Service provider.

[William Brogden]

You should also realize that many web service designs can be accomplished with a RESTful approach rather than SOAP. The "REST versus SOAP" argument has been ongoing for some time - try a google search for that phrase to see.

Giant web services such as Amazon, that started with a SOAP approach, have ended up supplying both REST and SOAP interfaces.

Bill