Author: dkulp
Date: Thu Apr 24 11:11:18 2008
New Revision: 651331

URL: http://svn.apache.org/viewvc?rev=651331&view=rev
Log:
Prepare release notes

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

Modified: 
incubator/cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt
URL: 
http://svn.apache.org/viewvc/incubator/cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt?rev=651331&r1=651330&r2=651331&view=diff
==============================================================================
--- 
incubator/cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt
 (original)
+++ 
incubator/cxf/branches/2.0.x-fixes/distribution/src/main/release/release_notes.txt
 Thu Apr 24 11:11:18 2008
@@ -1,11 +1,9 @@
-Apache CXF 2.0.5 Release Notes
+Apache CXF 2.0.6 Release Notes
 
 1. Overview
 
-Apache CXF 2.0.5 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.
+Apache CXF 2.0.6 delivers the latest set of patches for the 2.0.x series
+fixing another 21 reported JIRA issues.
 
 
 2. Installation Prerequisites 
@@ -80,50 +78,28 @@
 
 6. Specific issues, features, and improvements fixed in the 
 
-Release Notes - CXF - Version 2.0.5
-
+Release Notes - CXF - Version 2.0.6
 
 ** 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
-
-
-
-
+    * [CXF-918] - java code from wsdl2java for wrapped style if request and 
response have elements with the same names and different datatypes
+    * [CXF-1229] - Check for element name clash in request and response 
messages ignores setting of enableWrapperStyle
+    * [CXF-1388] - Error when running client generated by Wsdl2Java tool 
'org.apache.ws.commons.schema.constants.Enum$EnumValueException: Bad 
Enumeration value 'extension restriction''
+    * [CXF-1445] - Missing repository definition
+    * [CXF-1464] - xmlbinding error
+    * [CXF-1481] - PropertyEditor for class 
"org.apache.cxf.binding.soap.SoapVersion"  is wrong
+    * [CXF-1486] - wsdl2java generates aync SEI methods having compile errors 
when consuming a BARE service returning int.
+    * [CXF-1487] - WS-RM policy assertions not merged properly 
+    * [CXF-1488] - Synchronization issues in PolicyEngineImpl
+    * [CXF-1491] - ReadHeadersInterceptor reads to much after parsing 
soap-header and breaks wss signature
+    * [CXF-1492] - JAXB databinding adds classes recursively to JAXBContext. 
The reference impl. adds only the request and response classes.
+    * [CXF-1493] - Cannot  build 2.0.4 JBI Integration 
+    * [CXF-1496] - Wrong content type produced by CXF BC provider
+    * [CXF-1506] - No Implementation-Vendor in manifest
+    * [CXF-1515] - Bad Enumeration value 'extension restriction'
+    * [CXF-1523] - Reopen Bug CXF-1448: Aegis + SAAJ leads to namespace 
complaint.
+    * [CXF-1524] - SOAP with Attachments (BMMimeMultipart):  
DispatchInDatabindingInterceptor 's call to soapMessage.countAttachments() 
throws IOException 
+    * [CXF-1528] - DynamicClientFactory throws IllegalStateException due to 
JAXB not generating classes when unexpected schema element encountered in WSDL
+    * [CXF-1531] - support to publish the endpoint with multiple addresses 
which are starting with same context path
+    * [CXF-1534] - JAXWSMethodInvoker doesn't honour faultcode in thrown 
SoapFault
+    * [CXF-1537] - Out only out-of-band headers don't code gen correctly (with 
-exsh true) and runtime doesn't work with -exsh false
 


Reply via email to