The Spring Integration team is pleased to announce that the third milestone for the Spring Integration 5.0 release (
5.0.0.M3) is now available.
Initial implementation for a Spring Integration Testing Framework - the
@SpringIntegrationTestannotation for test classes and
MockIntegrationfactory help you to write unit tests for integration flows and channel adapters. We intend to flush out this capability with more features before GA, including more mocking, verifications and some
send-and-receiveutilities to test components in isolation. Feedback is welcome!
POJO handler method invocations (
@Transformeretc., or such methods invoked from XML definitions) now use
InvocableHandlerMethodby default. Together with the
@Defaultutilities that allows us to implement conditional method invocation scenarios based on the Content-Type and target method arguments resolution. To restore the previous SpEL-based behavior, the
@UseSpelInvokermethod-level annotation is provided.
A based on the WebFlux
ReactiveHttpRequestExecutingMessageHandlerimplementation is provided. Together with a
outputChanneloptions it provides backpressure manner for remote HTTP service consumption.
The (S)FTP (and AWS S3) Inbound Channel Adapters can now restore file tree locally. For that purpose a new,
RecursiveDirectoryScanneris introduced. The
useWatchServiceoption is also provided.
Web Services Gateways now can exchange
WebServiceMessages directly as the inbound/outbound
payload. This allows the support of MTOM via direct access to
UnmarshallingTransformercan now process a
MimeMessageas the payload to unmarshal it into an object graph with attachments.
The reply producing
MessageHandlernow has a fallback to the
replyChannelheader from the reply message, if there is no
replyChannelin the request message headers. This allows the implementation of business process-like scenarios when the next step is determined by the result of current calculations.