Project Status
This page is meant to help keep track of the status of various portions of CXF.
Basic Modules
Apache CXF™.
Web Services Standards Support Modules
CXF supports a variety of web service standards including SOAP, the WS-I Basic Profile, WSDL, WS-Addressing, WS-Policy, WS-ReliableMessaging, WS-Security, WS-SecurityPolicy, WS-SecureConversation, and WS-Trust.
Module | Filename |
|---|---|
| |
| |
| |
WS-Security, WS-SecurityPolicy, WS-SecureConversation, WS-Trust (client-side) |
|
cxf-rt-ws-mex-[version].jar |
Frontend Programming Modules
CXF supports a variety of "frontend" programming models.
Module | Filename | ||
|---|---|---|---|
Module | Status | Module name and/or notes | |
JAX-WS | Done - TCK compliant |
| |
| |||
JAX-WS frontendDone - TCK compliant |
| ||
Simple frontendDone |
| Javascript frontend |
|
Transport Modules
CXF includes its own transport abstraction layer to hide transport specific details from the binding and front end layers. Currently supported transports include: HTTP, HTTPs, HTTP-Jetty, HTTP-OSGI, Servlet, local, JMS, In-VM and many others via the Camel transport for CXF such as SMTP/POP3, TCP and Jabber.
Module | Filename | |
|---|---|---|
HTTP, ServletDone |
| |
JBI | Done | Top level integration directory |
JCA | Done | Top level integration directory |
JMX | Done | cxf-rt-management-2.2.10 |
Spring | Done | CXF uses Spring by default |
SOAP | Done |
|
Tooling | Done | cxf-tools-* |
WSDL 2.0 |
|
WS-*
Module | Status | Module name and/or notes |
|---|---|---|
WS-Addressing | Done | |
WS-Policy | Done | |
WS-RM | Finished except for outstanding JIRA issues | |
WS-Security | Done | |
WS-SecurityPolicy | Done | |
WS-SecureConversation | Done | |
WS-Trust | Client side done |
Databindings
| |
| |
HTTP-OSGI |
|
JBI (in CXF <2.5) |
|
| |
|
Protocol Binding Modules
...
Module | Filename | Notes |
|---|---|---|
| CXF feature that allows automatic detection of when a client and a service are stuck on the same bus and then bypasses much of the interceptor chains during processing. | |
CORBA |
| in CXF <3.3 |
HTTP |
|
|
object |
| CXF feature that allows (when combined with the local transport), directly passing objects from client/server in the same bus without marshalling. |
|
| |
|
|
Data Binding Modules
Data bindings implement the mapping between XML elements and Java objects. Data bindings convert data to and from XML, produce XML schema, and provide support for wsdl2java code generation. Not all data bindings support all of this functionality. At very least, a data binding must provide the data conversion.
Module | Filename | |||
|---|---|---|---|---|
| ||||
| ||||
Module | Status | Module name and/or notes | ||
JAXB | Finished | cxf-rt-databinding-jaxb | ||
XFire Aegis Databinding | Ported |
| ||
Done |
| SDO |
|
General Modules
...
Common SchemasDone |
| |
JIBX | GSoC project not yet integrated into CXF http://github.com/nilupa/cxf |
|
Castor |
|
Transports
| |
Common Utilities |
|
Core |
|
Javadoc |
|
Javascript |
|
JBI Bindings (in CXF <2.5) |
|
JBI (in CXF <2.5) |
|
JCA |
|
| |
Manifest |
|
Schema validation used for Aegis |
|
| |
| |
CXF uses Spring by default |
Outstanding Modules
...
Module | Status | |
|---|---|---|
JIBX | ||
WSDL 2.0 | ||
Castor | ||
WS-Atomic Transactions | ||
WS-Coordination | ||
WS-Eventing | ||
WS-BusinessActivity | ||
WS-Transfer | ||
Module | Status | Module name and/or notes |
HTTP | Finished | cxf-rt-transports-http |
HTTP-Jetty | Finished | cxf-rt-transports-http-jetty |
HTTP-OSGI | Finished | cxf-rt-transports-http-osgi |
JMS | Finished | cxf-rt-transports-jms |
Local | Finished | cxf-rt-transports-local |
Servlet | Finished |
|