Apache CXF 2.0.5 (incubating) Release Notes

1. Overview

Apache CXF 2.0.5, under incubation,  delivers the third milestone of 
the Celtix project (http://celtix.objectweb.org) and the XFire project
(http://xfire.codehaus.org) merge.  This release is mostly a patch release
from 2.0.4 fixing 34 JIRA issues as well as enhancing startup performance.


2. Installation Prerequisites 

Before installing Apache CXF (incubating), make sure the following products,
with the specified versions, are installed on your system:

    * Java 5 Development Kit   (Java 6 requires extra setup)
    * Apache ant 1.6

2.1 Java 5 Development Kit

You must install the J2SE Development Kit (JDK) 5.0, which can be downloaded
from:

    http://java.sun.com/j2se/1.5.0/download.jsp

After installing the JDK, set or modify the following environment variables:

    * JAVA_HOME -- set this environment variable
      to point at the root directory of the JDK 5.0 installation.

    * PATH -- make sure that your PATH includes: 
      %JAVA_HOME%\bin  (Windows) 
      $JAVA_HOME/bin   (UNIX)

If using a Java 6 kit, you may need to copy the jaxb-*, saaj-*, jaxws-* jars 
from the lib dir to your jre/lib/endorsed directory.


2.2 Apache Ant 1.6.5 (or newer, 1.7.0 should work as well)

To run samples included in the binary distribution of Apache CXF (incubating),
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.

For more details, see the Installation Guide.


2.3 Bouncy Castle/JCE requirement for WS-Security

To use the WS-Security features of CXF, you need to obtain a JCE crypto provider
that implements the algorithms that you plan to use. One option is to download 
the Bouncy Castle jar from:
http://bouncycastle.org/download/bcprov-jdk14-136.jar 
and add that to the lib directory or classpath.   



3. Building the Samples

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

4. Errata

4.1 WS-Security
The WS-Security configuration mechanisms may change between this release and 
the next one as we add in support for WS-SecurityPolicy and WS-Trust.

5. Reporting Problems

If you have any problems or want to send feedback of any kind, please e-mail the
cxf dev list, cxf-dev@incubator.apache.org.  You can also file issues in JIRA at:

http://issues.apache.org/jira/browse/CXF

6. Specific issues, features, and improvements fixed in the 

Release Notes - CXF - Version 2.0.5


** Bug
    * [CXF-907] - WSDLToJava fails to generate parameter for request header
    * [CXF-935] - Provider not working when its WSDL is supplied from spring configuration.
    * [CXF-1020] - WSDL2Java tool error: failed to generate codes with twoHeadersSameNameDifferentNamespace
    * [CXF-1247] - WSDLValidator does not use CatalogResolver to reslove wsdl 
    * [CXF-1269] - Using contentType = "application/octet-stream" on returned Datahandler/DataSource causes an InputStream to be left open
    * [CXF-1386] - java2wsdl: NullPointerException on @WebService interface throwing custom Exception
    * [CXF-1401] - More shutdown problems with jetty
    * [CXF-1408] - Data not returned if /tmp/cxf-tmp-#### deleted
    * [CXF-1412] - In  ClientFaultConverter', setStackTrace() throws NullPointerException if 'ss' String is null
    * [CXF-1417] - SOAPFaultException built programmatically and thrown in a JAX-WS handler are not correctly populated
    * [CXF-1418] - Problem having multiple interceptors of the same type on the interceptor chain
    * [CXF-1419] - JMS Server Response headers not populated properly
    * [CXF-1420] - LogUtils.log fails when trying to log an error with a question mark.
    * [CXF-1429] - Memory Leak at PolicyEngineImpl
    * [CXF-1430] - ThreadLocal Memory leak in HandlerChainInvoker
    * [CXF-1432] - Throwables should be serializable
    * [CXF-1433] - WS-Security vulnerability
    * [CXF-1435] - BusApplicationContext should pass empty String array to super constructor instead of null
    * [CXF-1436] - Error in WS-Security 1.1 Signature Confirmation handling
    * [CXF-1437] - schemas without *.xsd extensions being fetched from the internet instead of locally
    * [CXF-1438] - AttachmentDeserializer is leaving behind temp files
    * [CXF-1439] - WSDL2Java generates NPE for certain WSDL
    * [CXF-1442] - Clients only handle a single Session cookie
    * [CXF-1444] - JBIOutWrapperInterceptor fails to find objects sequentially 
    * [CXF-1446] - null pointer in java2wsld
    * [CXF-1448] - Aegis + SAAJ leads to namespace complaint.
    * [CXF-1456] - Investigate a more sensible set of default cipher suites
    * [CXF-1465] - WSDL2Java error when using <jaxb:serializable/> binding customization
    * [CXF-1467] - CXF Bug 1435 Not Resolved
    * [CXF-1468] - JBIWrapperOutInterceptor miss message type attribute for JBI binding
    * [CXF-1469] - NPE with Spring 2.5.2

** Improvement
    * [CXF-1272] - Application doesn't start up without internet connection (when providing <http-conf:conduit> setting)
    * [CXF-1484] - JBI binding should throw more meaningful exception instead of NPE when there is no operaiton in the JBI MessageExchange

** New Feature
    * [CXF-490] - Create CXF OSGi Bundles