- Added markMessageFromGroup to MessageGroup interface
- made ResequencingMessageGroupProcessor return the partial sequence that was processed
- removed obsolete test
- refactored CorrelatingMessageHandler to deal with the partially processed sequence properly
Still it is needed to remove the release-strategy attribute from the namespace to avoid confusion.
- also introduced testcase based on suggestion from Jettro (see issue)
- leaving a TODO for the awkwardly placed return statement (AbstractMessageSplitter needs more rigorous cleanup which I'll tackle separately)
- factored out completeGroup and expireGroup methods
- cleaned up imports
- some formatting
- added javadoc to CorrelationStrategy
Note on the CorrelationStrategy changes:
According to Postel's law it is right for the CorrelatingMessageHandler to do a null check for the result of the CorrelationStrategy, but it is also a good idea to throw a more meaningful exception from the strategy itself. We cannot enforce this in the contract without inconveniencing the users, so we don't.
- Upgrade to version 2.0 of the maven-release-plugin in order to
get the new 'update-versions' goal, which allows for doing nothing
other than updating pom versions - no tagging, no checkins, etc.
- Accommodate idiosyncracies of the plugin. When running for the first
time, it became clear that update-versions not only updates versions
as advertised, but also formats certain elements of the pom.
Committing just those format changes now so that future actual version
updates will not have to deal with this uninvited 'help'.
- How to run the command:
mvn --batch-mode release:update-versions -DdevelopmentVersion=2.0.0.M7
This will edit the <version> elements in the poms of the projects listed
in the root pom's <modules> section.
Upon updating to 3.0.4 the build fails with SpEL error code EL1004E when
executing test method shouldFindSimpleAggregatorMethodWithArray().
Reverting for now, but SPR-7519 has been created for tracking what
appears to be a minor SpEL regression.
- template.mf files now declare range [3.0.3, 4.0.0) for all Spring dependencies
- pom.xml files reverted to dependence on 3.0.3.RELEASE
