Page History

...

2.0.12 was the last version of 2.0.x to be released at Apache. It is now considered unsupported. Users are highly encouraged to migrate to newer versions of CXF.

CXF version 2.1.x

These should just be a bug fix releases for bugs users encounter with 2.1.x versions. These will be done on a branch by selectively merging fixes from trunk on an as-needed basis. For the most part, there would be fixes for:

• XFire migration issues
• Any interopability issues
• Critical show stoppers
• etc....

However, some new features have been back ported from the 2.2 branch (trunk) to provide some new functionality to users quicker. These include:

...

9 was the last version of 2.1.x to be released at Apache. It is now considered unsupported. Users are highly encouraged to migrate to newer versions of CXF.

CXF version 2.2.x

These should just be a bug fix releases for bugs users encounter with 2.2.x versions. These will be done on a branch by selectively merging fixes from trunk on an as-needed basis. For the most part, there would be fixes for:

...

• JAX-RS 1.1 (providing spec is finalized and TCK available)
• JAX-WS 2.2 (providing spec is finalized and TCK available)
• SOAP/TCP support (GSoC project)
• SOAP/JMS spec compliance (GSoC project)
• SDO databinding (GSoC project)
• Additional Annotation driven development/configuration

...

Future version - some will likely go into 2.3

• JAX-WS 2.2 (providing spec is finalized and TCK available)
• SOAP/TCP support (GSoC project)
• JiBX databinding (runtime, tooling is lower priority)
• Better Acegi integration
• Update to WS-RM 1.1
• Enhancements to WS-Trust support (STS possibly, SAML2 support through new WSS4J, etc...)
• Other WS-* stuff