Spring Web Services 5.1.0 M1 Release Notes

Spring Web Services 5.1.0-M1 Release Notes

Upgrading from Spring Web Services 5.0

Deprecations from Spring Web Services 5.0

Classes, methods, and properties that were deprecated and marked for removal in 5.1 have been removed in this release. Please ensure that you aren’t calling deprecated methods before upgrading.

Ordering of Strategies with @Order

Strategies resolved from the application context are now sorted with AnnotationAwareOrderComparator rather than OrderComparator. Previously only the Ordered interface was taken into account and an @Order annotation was ignored; both are now honored.

This applies to:

• The endpoint adapters, endpoint mappings, and endpoint exception resolvers detected by MessageDispatcher.

• The SmartEndpointInterceptor beans detected by AbstractEndpointMapping and AbstractAddressingEndpointMapping.

Review your configuration for strategies that carry an @Order annotation. Such a strategy was previously treated as unordered and placed last, and now moves to the position it asks for. Ordering that you had arranged by declaring beans in a particular order may therefore change.

Note that an @Order annotation on the @Bean method declaring a strategy is still not taken into account, as resolving it requires an order source provided by the bean factory.

New and Noteworthy

Observability

Spring Web Services is now instrumented with the Micrometer Observation API, so that a single instrumentation produces both metrics and tracing spans for the web service exchanges that an application takes part in.

Observations are disabled by default and are recorded once an ObservationRegistry is configured:

• On the client side, set it on the WebServiceTemplate that performs the exchanges. Each exchange is recorded under the soap.client.requests name.

• On the server side, set it on the component that handles the incoming connections, such as WebServiceMessageReceiverHandlerAdapter for the HTTP transport, WebServiceMessageListener for JMS, or MailMessageReceiver for email. Each request is recorded under the soap.server.requests name.

Tracing information is propagated as request headers over the transports that support them, which makes a client exchange and the server-side handling of the corresponding request part of the same trace. It is not read on the server side for the HTTP transport, as the Servlet layer is instrumented already. On that transport, the soap.server.requests observation is recorded as a child of the http.server.requests observation.

See the reference documentation for more details.

Dependency Upgrades

Spring Web Services 5.1.0-M1 moves to new versions of several Spring projects:

• …​

Deprecations in Spring Web Services 5.1.0-M1

• PayloadRootUtils has moved from org.springframework.ws.server.endpoint.support to org.springframework.ws.support, the class in the original package is deprecated as a result.