What would be the advantages of using SWS compared to CXF ?
CXF is fully JAXWS compliant and has much more features that SWS afaik.
And you can also use spring to configure it ;-)
Cheers,
Guillaume Nodet
On Aug 23, 2007, at 7:13 PM, larry hughes wrote:
That's great to hear. On a side topic, I have another team that is
planning
on providing their web services using the new Spring Web Service
framework.
Any ideas on how this fits into the servicemix scheme of things (BC/
SE)
since SWS is basically a replacement of CXF?
Larry
gnodet wrote:
ServiceMix and CXF are already integrated, though there is still some
work going on.
Two new components will be available in 3.2, a binding component and
a service engine.
The SE will be the newer version of jsr181, while the BC is based on
CXF and thus will have support for Reliable Messaging, WS-Policy,
etc...
If you were using JAX-WS annotated POJOs in jsr181, you should be
able to upgrade to servicemix-cxfse without too much problems
hopefully.
Cheers,
Guillaume Nodet
On Aug 20, 2007, at 8:48 PM, larry hughes wrote:
I've recently read on the Xfire site that they'd recommend using
CXF instead,
probably due to the move of XFire's author to Mule. How does this
affect
servicemix? Will the next servicemix depend on CXF instead of
XFire for
jsr-181? Just wondering what the upgrade path will look like for
WS down
the road.
Larry
--
View this message in context: http://www.nabble.com/CXF-integration-
tf4300789s12049.html#a12241701
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
View this message in context: http://www.nabble.com/CXF-integration-
tf4300789s12049.html#a12297855
Sent from the ServiceMix - User mailing list archive at Nabble.com.
