On April 16th 2008, Apache CXF graduated from the Apache incubator and officially became a top level project. At that time, CXF was mostly just a “soap stack”, although it did have a few additional bindings, such as as CORBA binding thanks to the contributions from IONA/Progress. Since then, the scope has expanded quite a bit. Top notch REST/JAX-RS support was added. Several new security specs were implemented. New services were added to CXF that uses the base framework. Things like WS-Discovery, a full STS, WS-Notification, and an XKMS implementation were added. The REST/JAX-RS implementation was enhanced to support several different API specs (wadl, swagger 2, openapi, etc…), various search providers, several types of “reactive” integrations, etc… We’ve recently received contributions to implement the MicroProfile client API’s.
Two sub-projects are now part of CXF as well. DOSGi is an implementation of the Distributed OSGi spec. Fediz is a security framework to implement WS-Federation Passive Requestor Profile and other specs to help secure your web application.
Over the last 10 years, we’ve done over 200 releases. We have 43 committers, 25 of which are PMC members. Many “mature” projects such as CXF have had to start thinking about entering the attic. Keeping a high level of involvement and forward progress for 10 years is not easy. CXF continues to receive new ideas, new features, fixes, etc… very often, constantly providing new releases for users to use. Part of this is due to the high level of adoption of CXF. Many companies rely on CXF for their WebService and REST needs. Companies like Talend, RedHat, WSO2, IBM, Savoir Technologies, Tomitribe, etc… rely heavily on CXF. Their users need CXF to “just work” as well as keep up with new technologies, specs, and features. Several of these companies pay some of their employees to contribute and support CXF. Tons of thanks go out to those companies for helping make CXF the success that it has become.
It’s been an exciting 10 years and I look forward to seeing what the future reveals.
This past week, the Apache CXF team released the latest patch for the 2.2.x series: 2.2.2. Normally, patch releases aren’t very exciting. Usually just a bunch of bug fixes. However, this release provides two extremely noteworthy bullets:
- JAX-RS 1.0 – 2.2.2 is the first release of Apache CXF to pass the JAX-RS 1.0 TCK. The 2.1.x versions of Apache CXF introduced some preliminary versions of JAX-RS based around the 0.6 and 0.8 versions of JAX-RS. 2.2.0 updated the basica API’s to 1.0 level, but was not fully JAX-RS 1.0 compliant. We finally got access to the TCK a short while ago and 2.2.2 includes all the patches and fixes necessary to get CXF to pass the 1.0 TCK. We still have a bunch of ideas and plans to make the REST/JAX-RS support in CXF even better, but passing the TCK is an exciting milestone.
- JBoss-WS – the JBoss WebServices team released JBossWS-CXF 3.1.2 based on Apache CXF 2.2.2. This release of JBossWS-CXF is the first to completely pass the various JAX-WS/JWS/SAAJ/JAXR parts of the J2EE CTS/TCK. This is just the first results of the JBoss/CXF collaboration. To achieve this, JBoss did identify and submit patches for several issues in CXF. They also done extensive testing with their own stack, .NET, and others to make sure CXF will completely meet their needs. JBossWS-CXF 3.1.2 is a result of all of that, but it’s also just a beginning. Now that the TCK is passing, we hope to expand the collaboration into more than just “tck bug fixes” with new features, new ideas, etc…
Anyway, definitely another exciting week for Apache CXF. Many thanks go out to the entire Apache CXF team, the JBoss folks that identified and fixed issues, and the Progress FUSE team for helping with the testing and development.
Just received this piece of email from Jim Jagielski:
I am happy and proud to announce that at this month’s board
meeting, we have approved CXF’s graduation out of the Incubator
and as a TLP. Dan Kulp was approved as VP of the PMC.
Congrats to one and all!
Pretty exciting. After 20+ months of hard work, the Apache CXF community finally graduates out of the incubator.