Release Notes - Spring Web Services - Version 1.0 M2 - HTML format

Bug

  • [SWS-31] - MessageHandlerAdapter uses J2EE 1.4
  • [SWS-32] - SaajSoapMessage does not work if content type includes parameters
  • [SWS-33] - CastorMarshaller is missing a way to specify the Castor-generated class to use during unmarshalling.
  • [SWS-35] - validation error for valid xml
  • [SWS-37] - Weblogic 8.1 throws javax.xml.soap.SOAPException: There should be only one Content-Type MimeHeader
  • [SWS-42] - Content-Type Header for SOAP Attachments misses required entries
  • [SWS-48] - Airline sample readme.txt has wrong dir info
  • [SWS-49] - Axis 1 Saaj implementation does not set Content-Type on saveChanges()

Improvement

  • [SWS-30] - Add C# WS-Security client
  • [SWS-36] - JibxMarshaller does not support unmarshalling of DOMSources and SAXSources
  • [SWS-38] - Make sure AbstractStaxEndpoint checks whether a StaxSource is used
  • [SWS-40] - Validation of xml in XmlBeansMarshaller
  • [SWS-41] - Add Echo sample client
  • [SWS-43] - Make PayloadValidatingInterceptor more customizable
  • [SWS-44] - schemaS element for PayloadValidatingInterceptor missing
  • [SWS-46] - Improve validation schema loading

New Feature

  • [SWS-27] - Upgrade to SAAJ 1.3
  • [SWS-29] - Transforming Interceptor
  • [SWS-34] - Extend creation of XStream
  • [SWS-47] - Dynamic WSDL address locations
  • [SWS-50] - Plain Old Xml (POX) support

Task

  • [SWS-28] - Maven2 build
  • [SWS-45] - Add a note on memory usage and perfomance impact in "Securing your Web services with Spring-WS" chapter of reference documentation

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.