diff --git a/docs/src/reference/docbook/whats-new-in-2.xml b/docs/src/reference/docbook/whats-new-in-2.xml index 8c7875824e..748d536df7 100644 --- a/docs/src/reference/docbook/whats-new-in-2.xml +++ b/docs/src/reference/docbook/whats-new-in-2.xml @@ -2,21 +2,21 @@ - What's new in Spring Integration 2.0 + What's new in Spring Integration 2.0?
Spring 3 support - Spring Integration 2.0 is built on top of Spring 3.0.5 and uses many new features of Spring 3 + Spring Integration 2.0 is built on top of Spring 3.0.5 and makes many of its features available to our users.
- Support for Spring Expression Language (SpEL) + Support for the Spring Expression Language (SpEL) - You can now use SpEL expressions within the transformer, router, filter, - splitter, aggregator, service-activator, and many more elements of the + You can now use SpEL expressions within the transformer, router, filter, + splitter, aggregator, service-activator, header-enricher, and many more elements of the Spring Integration core namespace as well as various adapters. - There are many samples provided throughout this document. + There are many samples provided throughout this manual.
@@ -25,18 +25,22 @@ You can now benefit from Conversion Service support provided with Spring while configuring many Spring Integration components such as Datatype Channel. - See as well + See as well . + Also, the SpEL support mentioned in the previous point also relies upon the ConversionService. Therefore, you + can register Converters once, and take advantage of them anywhere you are using SpEL expressions.
- TaskScheduler, Trigger and Poller + TaskScheduler and Trigger - TaskScheduler, Trigger and Executor support that was provided with Spring Integration 1.0 was - moved to Spring 3 core API and you can now benefit from reusing the same components within the entire - Application Context (not just Spring Integration configuration). Configuration of Poller was greatly simplified - as well by providing attributes for to directly configure rates, triggers and delays. See - for sample configuration. + Spring 3.0 defines two new strategies related to scheduling: TaskScheduler and Trigger + Spring Integration (which uses a lot of scheduling) now builds upon these. In fact, Spring Integration 1.0 + had originally defined some of the components (e.g. CronTrigger) that have now been migrated into Spring 3.0's + core API. Now, you can benefit from reusing the same components within the entire Application Context (not just + Spring Integration configuration). Configuration of Spring Integration Pollers has been greatly simplified + as well by providing attributes for directly configuring rates, delays, cron expressions, and trigger references. + See for sample configurations.
@@ -44,6 +48,7 @@ RestTemplate and HttpMessageConverter Our outbound HTTP adapters now delegate to Spring's RestTemplate for executing the HTTP request and handling its response. + This also means that you can reuse any custom HttpMessageConverter implementations. See for more details. @@ -59,30 +64,27 @@
Message History - We've provided implementation for the Message History pattern - allowing us - to keep track of all traversed components, including the name of each channel and endpoint as well as the timestamp - of that traversal. See for more details. + We now provide support for the Message History pattern + allowing you to keep track of all traversed components, including the name of each channel and endpoint as well as the timestamp + of that traversal. See for more details.
Message Store - We've provided implementation for the Message Store pattern. - The Message Store - provides a way to persist messages for any process that might take too long to happen in a single - transaction. Many sections of this document provide samples on how to use Message Store as it + We now provide support for the Message Store pattern. + The Message Store provides a strategy for persisting messages on behalf of any process whose scope extends beyond a single + transaction, such as the Aggregator and Resequencer. Many sections of this document provide samples on how to use a Message Store as it affects several areas of Spring Integration. See , - , , , for more details + , , , and for more details
Claim Check - We've provided implementation for the Claim Check pattern. - + We have added an implementation of the Claim Check pattern. The idea behind the Claim Check pattern is that you can exchange a Message payload for a "claim ticket" and vice-versa. This allows you to reduce bandwidth and/or avoid potential security issues when sending Messages across channels. See for more details. @@ -92,10 +94,10 @@
Control Bus - We've provided implementation for the Control Bus pattern which - - allows you to use messaging to manage and monitor endpoints and channels. - See for more details. + We have provided implementations of the Control Bus pattern which + allows you to use messaging to manage and monitor endpoints and channels. The implementations include both a SpEL-based approach + and one that executes Groovy scripts. + See and for more details.
@@ -104,53 +106,53 @@
New Channel Adapters and Gateways - We have added several new Channel Adapters and Messaging Gateways in Spring Integration 2.0 + We have added several new Channel Adapters and Messaging Gateways in Spring Integration 2.0. + +
+ TCP/UDP Adapters + + We have added Channel Adapters for receiving and sending messages over the TCP and UDP internet protocols. + See for more details. Also, you can checkout the following blog: + TCP/UDP support + +
+
Twitter Adapters Twitter adapters provides support for sending and receiving Twitter Status - updates as well as Direct Twitter Messages and perform Twitter Searches. See for more details. + updates as well as Direct Messages. You can also perform Twitter Searches with an inbound Channel Adapter. + See for more details.
XMPP Adapters - We've also added support for XMPP Messaging and Presence. See for more details. + The new XMPP adapters support both Chat Messages and Presence events. See for more details.
FTP/FTPS Adapters - File transfer support over FTP/FTPS has been added through FTP/FTPS adapters. See for more details. + Inbound and outbound File transfer support over FTP/FTPS is now available. See for more details.
SFTP Adapters - File transfer support over SFTP has been added through SFTP adapters. See for more details. + Inbound and outbound File transfer support over SFTP is now available. See for more details.
- -
- TCP/UDP Adapters - - We've added Channel Adapters for receiving and sending messages over internet protocols (TCP/UDP). See - for more details. - More information provided in the following blog: - TCP/UDP support - - -
Feed Adapters - We've added Channel Adapters for receiving news feeds (ATOM/RSS). See for more details. + We have also added Channel Adapters for receiving news feeds (ATOM/RSS). See for more details.
@@ -162,28 +164,31 @@ Groovy Support With Spring Integration 2.0 we've added Groovy support allowing you to - use Groovy scripting language to provide integration and business logic. See for more details. + use Groovy scripting language to provide integration and/or business logic. + See for more details.
-
+
Map Transformers - These symmetrical transformers convert payload objects to/from a Map. See for more details. + These symmetrical transformers convert payload objects to and from a Map. See for more details.
-
+
JSON Transformers - These symmetrical transformers convert payload objects to/from JSON. See for more details. + These symmetrical transformers convert payload objects to and from JSON. See for more details.
-
+
Serialization Transformers - These symmetrical transformers convert payload objects to/from byte arrays. See for more details. + These symmetrical transformers convert payload objects to and from byte arrays. + They also support the Serializer and Deserializer strategy interfaces that have been added as of Spring 3.0.5. + See for more details.
@@ -192,28 +197,31 @@
Framework Refactoring - ore API went through a major refactoring to make it simpler and more usable and although we anticipate - that the impact to the end user should be minimal please read through this document to find what was - changed especially. See , , , - , for more details. + The core API went through some significant refactoring to make it simpler and more usable. Although we anticipate + that the impact to the end user should be minimal, please read through this document to find what was + changed. Especially, visit , , , + , and for more details. If you are depending directly on some of + the core components (Message, MessageHeaders, MessageChannel, MessageBuilder, etc.), you will notice that you need to + update any import statements. We restructured some packaging to provide the flexibility we needed for extending the + domain model while avoiding any cyclical dependencies (it is a policy of the framework to avoid such "tangles").
-
- New SCM and Build Infrustructure +
+ New Source Control Management and Build Infrastructure - With Spring Integration 2.0 we've switched our build environment to use Git as SCM. To access our repository simply follow this URL: - http://git.springsource.org/+spring-integration. - Our build system was switched to Gradle. + With Spring Integration 2.0 we have switched our build environment to use Git for source control. To access our repository simply follow this URL: + http://git.springsource.org/spring-integration. + We have also switched our build system to Gradle.
New Spring Integration Samples - With Spring Integration 2.0 we've changed the distribution of our samples. Please read this blog to get more info + With Spring Integration 2.0 we have decoupled the samples from our main release distribution. Please read this blog to get more info New Spring Integration Samples - We alos created many new samples, including samples for every new Adapter. + We have also created many new samples, including samples for every new Adapter.
@@ -221,17 +229,17 @@ SpringSource Tool Suite Visual Editor for Spring Integration There is an amazing new visual editor for Spring Integration included within the latest version of SpringSource Tool Suite. - If you are not already using STS 2.5.1 please download it here + If you are not already using STS 2.5.1, please download it here: STS
- Upcomming Spring Integration ROO support + Upcoming Spring Integration ROO support - We've began working on Spring Integration ROO support which will be available with Spring Integration 2.0.1. + We have started working on Spring Integration ROO support, and plan to have a first milestone release soon. You can follow its development here: Spring Integration Roo Add-on.
- +