Apache CXF 2.0.12 Release Notes
Overview
Apache CXF 2.0.12 delivers the latest set of patches and bug fixes for Apache CXF 2.0.x. This release fixes 36 JIRA issues that have been reported by users.
Download
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
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)
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.
Bouncy Castle/JCE and Xalan 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.
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.
Errata
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.
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
ChangeLog
For a more detailed view of new features and bug fixes, see the
release notes.
|
|
|
CXF-2366
|
Allow for 1-way over JMS requests to set replyTo destination in JMS message when explicitly enabled
|
Daniel Kulp
|
Marat Gubaidullin
|
|
Closed
|
Fixed
|
Jul 28, 2009
|
Aug 03, 2009
|
|
|
CXF-2363
|
ReplyDestinationName settings not used in JMSDestination
|
Daniel Kulp
|
Daniel Kulp
|
|
Closed
|
Fixed
|
Jul 28, 2009
|
Aug 03, 2009
|
|
|
CXF-2361
|
Adding JBIBindingConfigure to configure the JBIBinding from the spring configuration
|
Willem Jiang
|
Willem Jiang
|
|
Closed
|
Fixed
|
Jul 26, 2009
|
Aug 03, 2009
|
|
|
CXF-2360
|
soap.xsd in the soapbinding has the wrong elements
|
Willem Jiang
|
Willem Jiang
|
|
Closed
|
Fixed
|
Jul 26, 2009
|
Aug 03, 2009
|
|
|
CXF-2359
|
wss4jin stuff is only verifying the first signature and first timestamp
|
Daniel Kulp
|
Daniel Kulp
|
|
Closed
|
Fixed
|
Jul 24, 2009
|
Aug 03, 2009
|
|
|
CXF-2357
|
The equals() method of JCA connection handle always return false.
|
Unassigned
|
William Tam
|
|
Closed
|
Fixed
|
Jul 24, 2009
|
Aug 03, 2009
|
|
|
CXF-2350
|
JBIConduitOutputStream should copy properties between JBI NormalizedMessage and cxf message invocation context
|
Freeman Yue Fang
|
Freeman Yue Fang
|
|
Closed
|
Fixed
|
Jul 22, 2009
|
Aug 03, 2009
|
|
|
CXF-2349
|
Space in namespace localName causes org.w3c.dom.DOMException: INVALID_CHARACTER_ERR
|
Daniel Kulp
|
Zack
|
|
Closed
|
Fixed
|
Jul 21, 2009
|
Aug 03, 2009
|
|
|
CXF-2348
|
MessageContext properties (HTTP_REQUEST_HEADERS & HTTP_RESPONSE_HEADERS) should not be available during all the phases of the invocation
|
Daniel Kulp
|
Guillaume Sauthier
|
|
Closed
|
Fixed
|
Jul 20, 2009
|
Jul 22, 2009
|
|
|
CXF-2344
|
attachment headers not copied into SAAJ message
|
Daniel Kulp
|
Daniel Kulp
|
|
Closed
|
Fixed
|
Jul 16, 2009
|
Aug 03, 2009
|
|
|
CXF-2343
|
Improve Message Performance Under High Volume with Low Latency Consumers
|
Daniel Kulp
|
Paul Hadrosek
|
|
Closed
|
Fixed
|
Jul 16, 2009
|
Aug 03, 2009
|
|
|
CXF-2327
|
[SoapBindingFactory] Verify QName properties before calling constructor
|
Daniel Kulp
|
Kenny MacLeod
|
|
Closed
|
Fixed
|
Jul 01, 2009
|
Aug 03, 2009
|
|
|
CXF-2318
|
Invalid message created when using MTOM and WS-RM
|
Daniel Kulp
|
Guillaume Porcher
|
|
Closed
|
Fixed
|
Jun 26, 2009
|
Aug 03, 2009
|
|
|
CXF-2317
|
NPE in WS-RM RetransmissionQueueImpl
|
Daniel Kulp
|
Guillaume Porcher
|
|
Closed
|
Fixed
|
Jun 26, 2009
|
Aug 03, 2009
|
|
|
CXF-2316
|
Allow JMS replyTo destination value be set on the outgoing messsage for a one-way call
|
Daniel Kulp
|
Marat Gubaidullin
|
|
Closed
|
Fixed
|
Jun 25, 2009
|
Aug 03, 2009
|
|
|
CXF-2302
|
HTTP continuations are not working correctly if keep-alives are on
|
Daniel Kulp
|
Daniel Kulp
|
|
Closed
|
Fixed
|
Jun 18, 2009
|
Aug 03, 2009
|
|
|
CXF-2292
|
Java first one-way operations generating faults
|
Daniel Kulp
|
Daniel Kulp
|
|
Closed
|
Fixed
|
Jun 16, 2009
|
Aug 03, 2009
|
|
|
CXF-2279
|
Current ConfigureImpl is not application refresh friendly
|
Willem Jiang
|
Willem Jiang
|
|
Closed
|
Fixed
|
Jun 11, 2009
|
Aug 03, 2009
|
|
|
CXF-2274
|
HTTP transport assumes UTF-8 instead of ISO-8859-1 if charset not specified
|
Daniel Kulp
|
Daniel Kulp
|
|
Closed
|
Fixed
|
Jun 09, 2009
|
Aug 03, 2009
|
|
|
CXF-2271
|
autoNameResolution not working for wrapper elements
|
Daniel Kulp
|
Daniel Kulp
|
|
Closed
|
Fixed
|
Jun 08, 2009
|
Aug 03, 2009
|
|