This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Spring-WS 1.0 M2 released

Sep 9th, 2006, 10:24 AM

Dear Spring community,

I'm pleased to announce that Spring Web Services 1.0 M2 has been released. 1.0 M2 is the second milestone of Spring-WS: a product of the Spring community focused on creating document-driven Web services.

Spring-WS 1.0 M2 includes support for Plain Old XML messages, SAAJ 1.3, SOAP 1.2, and further refinements. It also contains numerous fixes for issues discovered since 1.0 M1. Please see the changelog file (as well as the changelog in JIRA) for details.

Breaking changes
If you migrate your application from M1 to M2, you might have to change your code. Here is a list of the most important changes:

MessageHandlerAdapter has been renamed to MessageEndpointHandlerAdapter. The new name describes the function of the class better. You need to change this name in your *-servlet.xml application context files.

Jaxb2Marshaller has been moved to its own module spring-oxm-tiger. This was necessary to use because JAXB2 uses Java 1.5, and spring-oxm compiles with 1.3: I couldn't run the unit tests previously.

The org.springframework.xml package has been moved to a separate module. Necessary because spring-oxm now also depends on it.

All EndpointInterceptor implementations (including the PayloadValidatingInterceptor and PayloadLoggingInterceptor) have been moved to their own package (org.springframework.ws.endpoint.interceptor). The SOAP-specific SoapEnvelopeLoggingInterceptor has been moved to org.springframework.ws.soap.endpoint.interceptor.

EndpointMappings have been moved to separate packages as well. The non-SOAP specific PayloadRootQNameEndpointMapping (and subclasses) has been moved to org.springframework.ws.endpoint.mapping. The SOAP-specific SoapActionEndpointMapping has been moved to org.springframework.ws.soap.endpoint.mapping.

SOAP 1.1 and SOAP 1.2 specific features have been moved to seperate interfaces. For instance, there is a Soap11Body interface, which allows you to add SOAP 1.1-specific faults to a message.