Providing Spring Services as a SOAP Web Service

I have a fairly extensive Spring 3.0 service architecture (typical architecture, a bunch of model objects, and lots of services that do things with these objects). I would like to provide some of these services as SOAP web services.

We previously developed SOAP web services, but they were always relatively simple and focused, and we always used Axis 2. I found that Axis 2 is a bit heavy on the dependency and implementation side, and I'm a little worried that this will inflate my current project with something- then terrible.

I looked through and apparently using Apache CXF, that would be pretty easy. Therefore, I am looking for some advice on this. Does anyone have any practical experience? Advantages and disadvantages?

+4
source share
2 answers

We use spring with CXF for soap services, and it runs very smoothly. According to the CXF tutorial, this is simple use, just using the jaxws xml namespace.

+2
source

I have not tested any other webservice framework - I've always been with CXF, and I am very pleased with that.

If you use Netbeans (even if not, it is still useful, I would say), check out this guide: http://sites.google.com/site/apachecxfnetbeans/loanproc

Just skip the first few paragraphs (database integration, testing, etc. etc.) that you should already be aware of. Netbeans CXF integration is useful for writing fast clients using the built-in netbeans features.

amuses

0
source

All Articles