Spring Web Services eases the task of building contract-first SOAP services by using one of the many ways to manipulate XML payloads.
Spring Web Services includes best practices such as the WS-I basic profile, Contract-First development, and having a loose coupling between contract and implementation.
Developers can distribute incoming XML request to any object, depending on message payload, SOAP Action header, or an XPath expression.
Incoming XML messages can be handled in standard JAXP APIs such as DOM, SAX, and StAX, but also JDOM, dom4j, XOM, or even marshalling technologies.
Here are some key features of "Spring Web Services":
· Flexible XML Marshaling
· Reuses your Spring expertise
· Supports WS-Security
· Makes the Best Practice an Easy Practice
· Powerful mappings
· XML API support
· Integrates with Acegi Security
· Built by Maven
What's New in This Release: [ read full changelog ]
· Allow for custom ErrorHandler in PayloadValidatingInterceptor.
· Manifest files in 2.0.0 release are incorrect.
· ExceptionResolver order is reversed.
· Annotation-driven tag does not support ws-addressing @Action.
· EndpointExceptionResolver is not registered automatically when used together with <sws:annotation-driven/> tag.
· XomPayloadMethodProcessor is not added methodReturnValueHandlers in DefaultMethodEndpointAdapter.
· Support @Secured for @PayloadRoot methods.
· SOAP Envelope prefix.
· Improve the Maven archetype.
· Allow for bean references inside the <interceptors> namespace element.
· Make the locationURI in dynamic wsdls mandatory.
· Print SOAP message if validation fails.
· Fix broken references in the reference doc.