Author: dkulp
Date: Wed Jul 29 12:52:18 2009
New Revision: 798879

URL: http://svn.apache.org/viewvc?rev=798879&view=rev
Log:
Update release notes for 2.0.12

Modified:
    cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt

Modified: 
cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt
URL: 
http://svn.apache.org/viewvc/cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt?rev=798879&r1=798878&r2=798879&view=diff
==============================================================================
--- cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt 
(original)
+++ cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt 
Wed Jul 29 12:52:18 2009
@@ -1,9 +1,13 @@
-Apache CXF 2.0.11 Release Notes
+Apache CXF 2.0.12 Release Notes
 
 1. Overview
 
-Apache CXF 2.0.11 delivers the latest set of patches for the 2.0.x series
-fixing another 35 reported JIRA issues.
+Apache CXF 2.0.12 delivers the latest set of patches for the 2.0.x series
+fixing another 32 reported JIRA issues.
+
+IMPORTANT NOTE:  2.0.12 is the last scheduled release for the 2.0.x series of 
+Apache CXF.   Users are VERY strongly encouraged to upgrade to the 2.2.x 
+series as soon as possible.
 
 
 2. Installation Prerequisites 
@@ -68,46 +72,48 @@
 
 6. Specific issues, features, and improvements fixed in this version:
 
-** Sub-task
-    * [CXF-2110] - Missing parameterOrder attribute in java2wsdl generated RPC 
wsdls
-    * [CXF-2114] - java2ws generates invalid import statement when using 
member classes
-
 ** Bug
-    * [CXF-973] - WebFault(faultBean="...") not used
-    * [CXF-1999] - HTTP conduit configuration is not loaded when not using 
Spring
-    * [CXF-2025] - Null Pointer Exception in AbstractInvoker.createFault()
-    * [CXF-2030] - JMS transport is not usable with IBM MQI interface endpoints
-    * [CXF-2033] - StaxUtils assumes DOM Node::appendChild(c) returns the 
passed-in child
-    * [CXF-2034] - JMS client transport (JMSConduit) does not tear down its 
reply awaiting listener on Bus shutdown
-    * [CXF-2037] - SoapFault subcode not outputted correctly in 
Soap12FaultOutInterceptor
-    * [CXF-2038] - changes for signaturePropFile and decryptionPropFile of 
WSS4JInteceptor can't be reloaded if we use cxf in container
-    * [CXF-2049] - Temporary files are not deleted under windows
-    * [CXF-2050] - MimeBodyPartInputStream never finishes reading certain 
streams
-    * [CXF-2062] - MTOM content-type header missing required "type" parameter
-    * [CXF-2067] - Can't send message attachments via the WebServiceContext in 
2.0.x
-    * [CXF-2077] - When using wsdl2java with the -db xmlbeans flag, the 
generated build.xml doesn't work OOTB
-    * [CXF-2082] - client using decoupled ws-addressing with async handler 
hang from time to time
-    * [CXF-2084] - AbstractMessageResponseTimeInterceptor has protected 
methods, but default (package) scope constructor
-    * [CXF-2087] - CXFServlet / URIResolver tries to load file "" (empty file 
name)
-    * [CXF-2104] - Caller application hangs in case it uses the polling 
(Response) method with JAX-WS async mapping and an http error occurs during 
sending. In case of callback style (AsyncHandler), the client application has 
no way of getting the exception.
-    * [CXF-2105] - The CxfBusLifeCycleManager can cause 
ConcurrentModificationExceptions to be thrown
-    * [CXF-2106] - Temp files created for data over 64kb are never deleted
-    * [CXF-2115] - refactor JBIConduitOutputStream exception handle
-    * [CXF-2145] - Proxy in JCA connector throws exception due to concurrency 
issues
-    * [CXF-2149] - java.lang.ArrayStoreException getting headers in handler
-    * [CXF-2152] - Certain Spring AOP proxies cannot be used any more as 
service bean since CXF 2.1.4 because the real (non-proxy) target class is not 
found correctly by SpringAopClassHelper
-    * [CXF-2161] - WSA handler class MAPCodec is not decoding From header
-    * [CXF-2163] - org.apache.cxf.resource.URIResolver on Websphere 6.1 
doesn't resolve from "wsjar:" base URI's
-    * [CXF-2172] - RPC/Lit types with both XmlType and XmlRootElement are 
ending up as element parts, not type parts
+    * [CXF-2184] - XSD import statements do not apply given confguration
+    * [CXF-2203] - AttachmentSerializer content id incorrect
+    * [CXF-2205] - Aegis databinding always trims strings
+    * [CXF-2207] - JMS Transport send MTOM message as a TextMessage. The 
attachment becomes wrong.
+    * [CXF-2210] - Change Jsr250BeanPostProcessor bean defination in cxf.xml
+    * [CXF-2211] - Investigate possible OOM exception caused by Continuations
+    * [CXF-2212] - SAAJInInterceptor creates a SAAJ SOAPFault with only one 
"Detail" child
+    * [CXF-2213] - Currently CXF always produces true/false value for for 
mustUnderstand attribute irrespective of the SOAP version on the wire
+    * [CXF-2243] - JMSFactory.createJmsListener does not use property from 
JMSConfiguration to set the receiveTimeout on the constructed Spring DMLC
+    * [CXF-2271] - autoNameResolution not working for wrapper elements
+    * [CXF-2274] - HTTP transport assumes UTF-8 instead of ISO-8859-1 if 
charset not specified
+    * [CXF-2279] - Current ConfigureImpl is not application refresh friendly
+    * [CXF-2292] - Java first one-way operations generating faults
+    * [CXF-2302] - HTTP continuations are not working correctly if keep-alives 
are on
+    * [CXF-2317] - NPE in WS-RM RetransmissionQueueImpl
+    * [CXF-2318] - Invalid message created when using MTOM and WS-RM
+    * [CXF-2344] - attachment headers not copied into SAAJ message
+    * [CXF-2348] - MessageContext properties (HTTP_REQUEST_HEADERS & 
HTTP_RESPONSE_HEADERS) should not be available during all the phases of the 
invocation
+    * [CXF-2349] - Space in namespace localName causes 
org.w3c.dom.DOMException: INVALID_CHARACTER_ERR
+    * [CXF-2357] - The equals() method of JCA connection handle always return 
false.  
+    * [CXF-2359] - wss4jin stuff is only verifying the first signature and 
first timestamp
+    * [CXF-2360] - soap.xsd in the soapbinding has the wrong elements
+    * [CXF-2363] - ReplyDestinationName settings not used in JMSDestination
 
 ** Improvement
-    * [CXF-2042] - Expose totalHandlingTime attribute in 
ResponseTimeCounterMBean to offer trendsup monitoring
-    * [CXF-2063] - should set catalogManager debug level a bit ealier
-    * [CXF-2081] - Allow specifying a Java heap size when wsdl2java -compile 
invokes Java compiler
-    * [CXF-2140] - Allow injection of an existing MBeanServer into the 
InstrumentationManagerImpl
-    * [CXF-2141] - Expose faults count in ResponseTimeCounter in addition to 
existing invocations count
-    * [CXF-2169] - JBIConduitOutputStream need save JBI MessageExchange in 
response message for later possible use
-    * [CXF-2181] - Dynamic Dispatch classes should cache MessageFactory 
instances
+    * [CXF-2113] - http:client configuration with Spring 
PropertyPlaceholderConfigurer
+    * [CXF-2186] - Validate WSS headers using new checkReceiverResultsAnyOrder 
method in WSHandler.
+    * [CXF-2246] - jaxws:endpoint should support to configure the transportId
+    * [CXF-2316] - Allow JMS replyTo destination value be set on the outgoing 
messsage for a one-way call
+    * [CXF-2327] - [SoapBindingFactory] Verify QName properties before calling 
constructor
+    * [CXF-2343] - Improve Message Performance Under High Volume with Low 
Latency Consumers
+    * [CXF-2350] - JBIConduitOutputStream should copy properties between JBI 
NormalizedMessage and cxf message invocation context
+    * [CXF-2361] - Adding JBIBindingConfigure to configure the JBIBinding from 
the spring configuration 
+    * [CXF-2366] - Allow for 1-way over JMS requests to set replyTo 
destination in JMS message when explicitly enabled
+
+
+
+
+
+
+
+
+
 
-** New Feature
-    * [CXF-2069] - provide services list that's easily parseable


Reply via email to