You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The Apache CXF team is proud to announce the 2.0-M1 incubating release!

This release includes the following features:

  • JAX-WS frontend
  • Java2WSDL and WSDL2Java tools
  • SOAP 1.1 & 1.2, XML and REST/HTTP bindings
  • JAXB 2.0 Databinding support
  • JSON support with Jettison
  • WSDL 1.1 support
  • WS-Addressing support
  • Support for MTOM and Soap with Attachments
  • HTTP, Servlet, JMS and Local Transports
  • Simple POJO service frontend
  • Javascript frontend
  • JBI Service Engine. CXF services can be deployed into any JBI compliant container (ServiceMix or OpenESB)
  • JCA 1.0 support, J2EE application can integrate with legacy application through JCA 1.0 support in CXF
  • Spring Support

Download

Download

Description

cxf-incubator-2.0-M1.tar.gz

GZip of the CXF binaries

cxf-incubator-2.0-M1.zip

Zip of the CXF binaries

cxf-incubator-2.0-M1-src.tar.gz

Gzip of the sources

Samples

To run samples included in the binary distribution of Apache CXF, you must install the Apache Ant 1.6.5 build utility, which can be downloaded from:

http://ant.apache.org/bindownload.cgi

After installing Apache Ant, add the <AntInstallDir>/bin directory to your PATH.

Building the samples included in the binary distribution is easy. Go to the samples directory and follow the build instructions in the README.txt file included with each sample.

Errata

  • There is an issue with Jetty HTTP that prevents Apache CXF from being able to shut down the actual port listener. If you programmatically remove the last endpoint published on a port, the listener remains running on the port, but only 404 (page not found) errors are served to subsequent client connections.
  • In certain cases nillable elements in XML Schema and xsi:nil attributes in XML documents may not work correctly. A bug has been logged with the JAXB team.
  • Due to bug 6467808 in the Java 1.5_09 JDK, you must ensure that no namespace declarations are overwritten in your SOAP messages. If a namespace declaration is overwritten in a SOAP message your process will fail with the following
    error message: ERROR: 'NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.'
  • Currently the JaxWsServiceFactoryBean requires you to explicitly set the BindingFactory to JaxWsSoapBindingInfoFactoryBean for the @SoapBinding annotation to work. Usage of the JAX-WS Endpoint should work regardless.

Whats not done yet?

There are many things we will be working on for the next version of CXF:

  • WS-ReliableMessaging, WS-Security
  • Improved tooling to support WSDL 2.0
  • Support for more databindings including XFire's Aegis databinding, JiBX, and XMLBeans
  • Asynchronous HTTP support
  • Performance optimizations - CXF is quite fast now, but we know of several performance improvements to be done for the next version.
  • JBI Binding Components
  • Tuscany Support
  • Geronimo Integration
  • Improved Documentation
  • See the CXF Roadmap for more information.

Upgrading from XFire

Currently, it is not recommended that all XFire users upgrade to CXF at this time. For more information, see the XFire Migration Guide.

Upgrading from Celtix

Currently it is not recommended that all Celtix users upgrade to CXF at this time. For more information, see the Celtix Migration Guide.

  • No labels