Previously, `AggregatingMessageHandler#setExpireGroupsUponCompletion` had additional logic for removing complete MessageGroups. It could produce some overhead on application start-up with big persistent `MessageStore`. This logic played a role to remove empty groups from a `MessageStore`. Since `AbstractCorrelatingMessageHandler#forceComplete` has an ability to to remove empty groups too, this logic became redundant. So, to clean `MessageStore` from empty complete groups, it's sufficient to use a `MessageGroupStoreReaper`. * Remove logic iterating over the `MessageStore` from `AggregatingMessageHandler#setExpireGroupsUponCompletion` * Polishing `AggregatorSupportedUseCasesTests.java` to use `store.expireMessageGroups(0)` * Introduce `empty-group-min-timeout` xml-attribute, populating `AbstractCorrelatingMessageHandler#minimumTimeoutForEmptyGroups` * Add parser tests for `empty-group-min-timeout` attribute JIRA: https://jira.springsource.org/browse/INT-2899 INT-2899: Documentation about changes of ACMH * rename new XSD-attribute to `empty-group-min-timeout` * add to Reference Manual description about `empty-group-min-timeout` * add 'What's new' for `empty-group-min-timeout` * add 2.2-3.0 Migration Guide note INT-2899 Doc Polishing
Spring Integration
Checking out and Building
To check out the project and build from source, do the following:
git clone git://github.com/SpringSource/spring-integration.git
cd spring-integration
./gradlew build
If you encounter out of memory errors during the build, increase available heap and permgen for Gradle:
GRADLE_OPTS='-XX:MaxPermSize=1024m -Xmx1024m'
To build and install jars into your local Maven cache:
./gradlew install
To build api Javadoc (results will be in build/api):
./gradlew api
To build reference documentation (results will be in build/reference):
./gradlew reference
To build complete distribution including -dist, -docs, and -schema zip files (results will be in build/distributions)
./gradlew dist
Using Eclipse
To generate Eclipse metadata (.classpath and .project files), do the following:
./gradlew eclipse
Once complete, you may then import the projects into Eclipse as usual:
File -> Import -> Existing projects into workspace
Browse to the 'spring-integration' root directory. All projects should import free of errors.
Using IntelliJ IDEA
To generate IDEA metadata (.iml and .ipr files), do the following:
./gradlew idea
Resources
For more information, please visit the Spring Integration website at: http://www.springsource.org/spring-integration