netzooid

I’m very happy to announce that the CXF team has produced a 2.0 release candiate! This release has some real quality stuff in it:

• A JAX-WS implementation – although we aren’t quite TCK compliant yet.
• Built in support for WS-Addressing, WS-Policy, WS-RM, and WS-Security
• Really good Spring 2.0 integration
• Support for building web services from POJOs – i.e. no annotations
• HTTP, JMS, and local (in-JVM) transports
• RESTful services support – including JSON services

If you’re currently an XFire user, I would suggest you take a look. I think there is a lot to benefit from:

• Improved WSDL support
• Improved JAX-WS support
• Improved JMS transport
• Maven plugins
• Spring 2.0 syntax support
• Improved WS-* support
• Cleaned up APIs for building services
• Easier to use extension points
• RESTful support
• Support for a “bare” XML binding, which doesn’t include a SOAP envelope

Most XFire services that you have written should be compatabile out of the box with CXF. You will however have to change your deployment code or xml configuration to take advantage of the improved APIs and improved XML format. See the XFire migration guide for some more details.

There has been a question or two about why we are announcing a release candidate as people don’t often announce RCs. There are a couple reasons. First, we’re attempting to finish the JAX-WS TCK testing before we release 2.0 final – although that may wait until 2.0.1. So we wanted to give people a release to use in the meantime. Second, while we’ve had many users testing CXF, we’re sure there are a few bugs out there yet (people have already pointed out a couple which we’re working on fixing). We’d like to throw the release out to the wider community to run through the gauntlet before we declare 2.0 final.

This entry was posted on Sunday, May 6th, 2007 at 3:08 am and is filed under Javercising, Web Services.