Roadmap
Current Roadmap for future versions of CXF. (this This is an ongoing "work in progress", subject to change.) Note that a primary goal of the Apache CXF team is to make frequent CXF releases. This includes major, stabilized, and thoroughly tested releases, as well as minor patch releases.
Future version
...
These may find their way into one of the releases below if people step up to finish them.
- Support for additional MicroProfile APIs (e.g. OpenAPI)
- HTTP/2 Transport
- SOAP/TCP support (GSoC project)
- JiBX databinding (GSoC project)
- Castor databinding
- Better management capabilities
- Better Acegi integration
- Update to WS-RM 1.1
- Enhancements to WS-Trust support (STS possibly, SAML2 support through new WSS4J, etc...)
- Additional WS-* support; e.g., Quality of Service (WS-Atomic Transactions and WS-Coordination), bootstrapping (WS-MetaDataExchange), WS-BusinessActivity, WS-Eventing and WS-Transfer
- Support for Web Service Definition Language (WSDL) 2.0
- Enhanced IDE support for CXF (e.g., Eclipse, NetBeans, IntelliJ IDEA and JDeveloper) - these improvements are primarily performed by the IDE teams.
- Enhanced SOA test tool support for CXF (e.g. soapUI).
CXF version 2.4
Under development
| Wiki Markup |
|---|
CXF version 2.3.\[x\] |
New features are being developed here to be released "when ready". Features on the roadmap include:
- JAX-RS 1.1
- JAX-WS 2.2
- SOAP/JMS spec compliance (GSoC project)
- SDO databinding (GSoC project)
- Additional Annotation driven development/configuration
See the 2.3 Migration Guide for more details about new features and changes.
| Wiki Markup |
|---|
CXF version 2.2.\[x\] |
| Wiki Markup |
|---|
The CXF 2.2.\[x\] releases include bug fix releases for issues users encounter with 2.2.x versions. These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis. For the most part, there would be fixes for: |
You should also check the JIRA Road Map for the latest information.
CXF version 3.1.x
The CXF 3.1.x releases include bug fix releases for issues users encounter with 3.1.x versions. These releases will be done on a branch by selectively merging fixes from the trunk on an as-needed basis. For the most part, there would be fixes for:
...
- Interopability issues
- Critical show stoppers
Some new features may be back ported from trunk master to provide some new functionality to users quicker if it doesn't affect the existing stuff or can enhance some of the new features in 23.2.
| Wiki Markup |
|---|
Legacy CXF versions 2.1.\[x\] and 2.0.\[x\] - EOL |
| Wiki Markup |
|---|
2.1.10 was the last version of 2.1.x to be released at ASF. 2.0.13 was the last version of 2.0.x to be released at ASF. 2.1.\[x\] and 2.0.\[x\] are now considered end-of-life and are therefore unsupported. Users are highly encouraged to migrate to newer versions of CXF. |
Release Overview
A goal of the Apache CXF team is to make frequent CXF releases. This includes major, stabilized, and thoroughly tested releases, as well as minor patch releases.
...
...
Release Date
...
Notes and Info
...
2.4.0
...
Under Development
...
...
2.3.1
...
Under Development
...
...
...
Released October, 2010
...
...
2.2.12
...
Under Development
...
...
...
Released October, 2010
...
...
...
Released August, 2010
...
...
...
Released June 2010
...
...
...
Released May, 2010
...
...
...
Released March, 2010
...
...
...
Released January 23, 2010
...
...
...
Released November, 2009
...
...
...
Released October, 2009
...
...
...
Released August, 2009
...
...
...
Released May, 2009
...
...
...
Released April, 2009
...
...
...
Released March, 2009
...
...
...
Released and End-of-life
...
1.
See the 3.1 Migration Guide for more details about new features and changes.
Legacy CXF versions 3.0.x, 2.7.x, 2.6.x, 2.5.x, 2.4.x, 2.3.x, 2.2.x, 2.1.x, and 2.0.x - EOL
Versions of CXF prior to 3.1.x are no longer supported at Apache. They are now considered end-of-life and are therefore unsupported. Users are highly encouraged to migrate to newer versions of CXF.
...
...
Released and End-of-life
...