Spring Integration

Spring Integration builds upon how Spring Framework uses POJOs to manage a module's dependencies and allows developers to build reusable components with a higher level of complexity.

This library is an essential part if developers want to build enterprise-level software, writing code that adheres to the separation of concerns principle, is easy to test, and takes less time to debug and maintain.

Spring Integration comes with extensive JMX support, can be integrated with external systems, and also supports most of the software design patterns described in the Enterprise Integration Patterns book.

What is new in this release:

• DelayedMessageWrapper should be public in order to access the wrapped message from infrastructure code.

What is new in version 4.2.2:

• DelayedMessageWrapper should be public in order to access the wrapped message from infrastructure code.

What is new in version 4.1.6 / 4.2 Milestone 2:

• DelayedMessageWrapper should be public in order to access the wrapped message from infrastructure code.

What is new in version 4.1.4 / 4.2 Milestone 1:

• DelayedMessageWrapper should be public in order to access the wrapped message from infrastructure code.

What is new in version 4.1.3:

• DelayedMessageWrapper should be public in order to access the wrapped message from infrastructure code.

What is new in version 4.1.2:

• DelayedMessageWrapper should be public in order to access the wrapped message from infrastructure code.

What is new in version 3.0.0 M1:

• Provides a way to Catch/Handle TCP Adapter SocketTimeoutException.

What is new in version 2.1.3:

• ExpressionEvaluatingCorrelationStrategy is not BF aware so any correlation-strategy-expression that begins with @bean will fail
• Can't use payload-expression that's a Map when the Map's key is not a String.
• Unable to convert MessageHistory, MessageHeaders via bundled converters.

What is new in version 2.1.2:

• ConcurrentModificationException when using PriorityChannel due to Message header modification
• NIO ip:tcp-connection-factory leaks memory
• GemFire module: ForkUtil class should be OS-independent
• Fixed Bundlor Versions in 2.1.x
• <logging-channel-adapter> hasn't got 'order' attribute
• Memory leak in SimpleMessageStore.
• Fixed OSGi ranges for 2.1.x

What is new in version 2.2.0.M1:

• Dependency upgrades such as Spring 3.1.0.RELEASE, Spring AMQP 1.1.0.RELEASE, Spring Data Mongo 1.1.0.M1, Spring Gemfire 1.1.1.RELEASE
• JPA support
• Initial support for graceful shutdown of integration context
• Support for 'Publisher Confirms and Returns' based on new features of Spring AMQP

What is new in version 2.1.1:

• This is the first maintenance release of 2.1.x branch and contains the usual things like bug fixes and improvements related to AMQP, Gemfire, Mongo and Redis modules which were first introduced in Spring Integration 2.1.0.

What is new in version 2.1 RC1:

• outbound-channel-adapter should support the 'expression' attribute
• FileTransferringMessageHandler - Add support for writing files to a temporary directory
• Add support for Resource Loading inbound channel adapter
• Add support for expiring MessageGroups based on the idle time

What is new in version 2.1 M2:

• Refactored (simpler and more flexible) Aggregator/Resequencer
• An XPath filter
• Stored Procedure adapters
• AMQP-backed Message Channels

What is new in version 2.1 M1:

• AMQP/RabbitMQ: inbound and outbound adapters (one-way and request/reply)
• GemFire: MessageStore, Cache writing and listening adapters, and Continuous Queries driving inbound Messages
• Redis: MessageStore, Pub/Sub messaging adapters, and Pub/Sub-backed Message Channel
• MongoDB: MessageStore