VMware offers training and certification to turbo-charge your progress.Learn more
We are extremely pleased to announce that Spring Integration 3.0.0.RC1 is now available in the Spring Milestone Repo
This release uses Spring Framework 3.2.5 by default but is also compatible with Spring 3.1.x and 4.0.x.
The release notes, showing changes since milestone 3, are available here.
##First, a Note About Spring Framework 4 Support
Spring Framework 4.0 has a new
spring-messagingmodule that contains a number of key abstractions from Spring Integration.
Spring Integration 3, while being compatible with Spring Framework 4, does not depend on it, and does not use these classes, so that it can also be used with Spring Framework 3.2 and 3.1.
We are planning to release Spring Integration 4 in early 2014, which will be completely compatible with (and require) Spring Framework 4, utilizing its
spring-messagingmodule as a foundation. A milestone will be available very soon after Spring Framework 4 is released.
##What's New in 3.0
The complete "What's New" for the 3.0 release can be found in the Reference Documentation, but here are a few highlights...
###New and Modified Endpoints
<int-syslog:inbound-channel-adapter id="foobar" channel="foo" port="1514" />
<jmx:tree-polling-channel-adapter id="jmxtree" channel="mbeanData" auto-startup="false" query-name="java.lang:type=Runtime" query-expression="*:type=*"> <si:poller max-messages-per-poll="1" fixed-rate="5000"/> </jmx:tree-polling-channel-adapter>
<int-file:tail-inbound-channel-adapter id="tailer" channel="lines" file="/tmp/baz" />
<int:gateway id="myGateway" service-interface="foo.Bar" default-request-channel="requestChannel"> <int:default-header name="calledMethod" expression="#gatewayMethod.name"/> </int:gateway>
mputnow support recursion - allowing the transfer of a directory tree.
<chain/>can now have an id, allowing them to be made available as beans and/or _MBean_s
<int-ip:tcp-connection-event-inbound-channel-adapter channel="events" />
No output-channel or replyChannel header available_ChannelResolutionException_s.
<int:spel-function id="foo" class="foo.MyUtils" method="evaluate(java.lang.String, java.lang.Object)"/> <int:transformer input-channel="in" output-channel="out" expression="#foo(headers.bar, payload)" />
Two built-in functions are provided: #jsonPath and #xpath.
Custom _PropertyAccessor_s can also be added to the evaluation contexts.
Please see the project page for more information and links for downloads, documentation etc.
We will be releasing shortly, so we would appreciate users giving this release candidate a spin.
A number of migration considerations are detailed in the migration guide.