Apache CXF 2.2.10 Release Notes

1. Overview
 
Apache CXF 2.2.10 delivers the third major version of 
the Celtix project (http://celtix.objectweb.org) and the XFire project
(http://xfire.codehaus.org) merge.  This release is a major update from 
the 2.1.x series.   The major new additions include:

 * WS-SecurityPolicy
 * WS-SecureConversation
 * Partial support for WS-Trust
 * Initial support for JAX-RS 1.0 including a client API for accessing 
   REST services   

2.2.10 fixes over 55 JIRA issues reported by users and the community.


2. Installation Prerequisites 

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

    * Java 5 Development Kit
    * Apache ant 1.6

2.1 Java 5 Development Kit

You must install the J2SE Development Kit (JDK) 5.0 or 6, 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)

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,
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.


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. Reporting Problems

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

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


5. Migration notes:

See the migration guide at:
http://cxf.apache.org/22-migration-guide.html
for caveats when upgrading from CXF 2.1.x to 2.2.x.


6. Specific issues, features, and improvements fixed in this version

Release Notes - CXF - Version 2.2.10

** Bug
    * [CXF-2704] - CXF JAX-RS  "Content-Disposition" is lost for second multipart 
    * [CXF-2823] - REST Client sending all lowercase post parameters
    * [CXF-2841] - WS-RM returns an exception to the client even when its retry mechanim successfully delivers the message after some transmission error
    * [CXF-2842] -  wsa:action header is missing when the  wsam:Action="" in wsdl input
    * [CXF-2843] - The default wsa:action value computation for response message is not correct. 
    * [CXF-2844] - Typo on JAX-WS Configuration page: publishedEndpointURL should be publishedEndpointUrl
    * [CXF-2846] - JAXWS Provider endpoints do not work if either super classes implementing or interfaces extending Provider are used
    * [CXF-2847] - BigDecimalType incorrectly prints scientific notation
    * [CXF-2851] - Schemas passed by ServiceFactoryBean.setSchemaLocation() are not accessible in DataBinding model
    * [CXF-2852] - JavaToWS requires Spring
    * [CXF-2853] - XFire Migration Guide shows XMLBeans indicates not ported
    * [CXF-2856] - In some cases, use of http binding on the client results in "IllegalStateException (Already connected)"
    * [CXF-2857] - MTOM: JAX-RS response missing XOP attachment
    * [CXF-2861] - http-osgi transport doesn't set conduitInitiator correctly
    * [CXF-2865] - DispatchClientServerTest fails on Windows
    * [CXF-2867] - Skip wsa policy verification  when client proxy is created with AddressingFeature(required=false) 
    * [CXF-2868] - JAXB unmarshal error when the field  of  partTypeClass  is javax.xml.datatype.XMLGregorianCalendar
    * [CXF-2869] - have JAXBElementProvider look for @XmlJavaTypeAdapter on the interfaces
    * [CXF-2885] - Wrong import package version for javax.servlet
    * [CXF-2887] - JAXRS NullPointerException given null argument
    * [CXF-2891] - Invalid WSDL when using <jax-ws:schemaLocation> (XSD) with ASM in the classpath
    * [CXF-2892] - AttachmentSerializer outputs "xop+xml" as body content type even XOP is not enabled
    * [CXF-2893] - CXF should use class' classloader for initialization of its loggers
    * [CXF-2896] - URIResolver should decode spaces before trying to resolve URI from filesystem
    * [CXF-2900] - WSDLValidator through Stax2DOM leaves input streams open which causes input files to be locked.
    * [CXF-2902] - Doc-lit, bare, multi part ("type" and not any) message gets rejected by DocLiteralInInterceptor
    * [CXF-2906] - WS-Addressing replay/message ID uniqueness enforcement does not handle clustering or restarts
    * [CXF-2908] - Using a Java enum type in a JAX-RS matrix parameter results in a StackOverflowError when generating the WADL
    * [CXF-2909] - WS-T / WS-SP sp:RequestSecurityTokenTemplate not using  wst:SecondaryParameters
    * [CXF-2910] - Unable to use XmlSchema element as message part in WSDL
    * [CXF-2914] - Digest algorithm defined in WS-SecurityPolicy is not honored in WS-Security signature from client
    * [CXF-2915] - Client with WS-SecurityPolicy requiring an IssuedToken fails to include an issued SAML token in the WS-Security signature of the message
    * [CXF-2918] - URIParserUtil.getAbsoluteURL() does not return a nomalized url string
    * [CXF-2919] - NullPointerException at org.apache.cxf.staxutils.StaxUtils.writeNode(Node, XMLStreamWriter, boolean) when DOCTYPE is in a XML Schema
    * [CXF-2921] - PolicyBasedWSS4JInInterceptor not asserting TransportBinding assertion when no message layer security is added
    * [CXF-2936] - NullPointerException in ServerImpl combining JAX-RS and Simple Frontend

** Improvement
    * [CXF-2664] - STSClient overloaded setPolicy causes issues with Spring based STS client configuration
    * [CXF-2824] - Error handling improvements for invalid Soap message content
    * [CXF-2833] - Source jars for osgi jars should work in Eclipse PDE mode
    * [CXF-2837] - Add null pointer check in SoapOutInterceptor
    * [CXF-2855] - WSDL2Java JAX-WS XJC customizations
    * [CXF-2860] - Handle the soap fault inbound message in server side
    * [CXF-2862] - Provide an annotation to allow customisation of the elements declared in the request & response representation in the auto-generated wadl
    * [CXF-2863] - When 'useHttpsURLConnectionDefaultSslSocketFactory'  is true, the 'trustManagers' configuration is not truly ignored
    * [CXF-2884] - Client async invoke API should accept context and exchange parameters
    * [CXF-2886] - Add a blockPostConstruct property to JaxWsServerFactoryBean  
    * [CXF-2905] - Support sending WS-A 1.4 ActAs in requests from STS client.
    * [CXF-2907] - Allow DynamicClientFactory to use any JAXB version 2.1 or greater
    * [CXF-2923] - Logging{In|Out}Intererceptor should check the encoding before writing the log
    * [CXF-2928] - Add a configuration option that allows STSClient to use the requester's X509Certificate as the SubjectConfirmation KeyInfo data within RequestSecurityToken messages
    * [CXF-2929] - Allow programmatic initialisation of RMManager
    * [CXF-2931] - Add configurable pretty printing to the CXF logging in/out interceptors


** Task
    * [CXF-2836] - JAXWS2.2: Generate proper wsa:action header for dispatch instance when AddressinfFeature is enabled
    * [CXF-2840] - JAXWS2.2: Process the EPR in WSDL
    * [CXF-2850] - Throw correct SOAPFaultException when the wsa addressing header is missing 


