This website requires JavaScript.
Explore
Help
Sign In
Spring
/
spring-integration
Watch
1
Star
0
Fork
0
You've already forked spring-integration
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
0ec6cd61d9521456cf696127f306813bbe874f00
spring-integration
/
org.springframework.integration
History
Mark Fisher
0ec6cd61d9
SimpleDispatcher no longer continues to retry sending any time it catches an Exception. Instead, it will try to send to each of its targets until one of them accepts the message (returns true). If a target returns false (e.g. for a timeout) or throws a MessageRejectedException (e.g. a MessageSelector did not accept the Message), then it will continue trying its other targets. However, any other Exceptions will be re-thrown immediately. Also, it no longer attempts to send to its targets more than once. Thus, the 'rejectionLimit' and 'retryInterval' properties have been removed. The retry behavior actually belongs in an interceptor/template on a per-MessageTarget basis. Some targets are retry-able (e.g. might throw a RemoteAccessException), but others are not. Therefore, the SimpleDispatcher should not have this awareness; such configuration options belong with the individual target instead (part of INT-337).
2008-08-18 19:36:04 +00:00
..
src
SimpleDispatcher no longer continues to retry sending any time it catches an Exception. Instead, it will try to send to each of its targets until one of them accepts the message (returns true). If a target returns false (e.g. for a timeout) or throws a MessageRejectedException (e.g. a MessageSelector did not accept the Message), then it will continue trying its other targets. However, any other Exceptions will be re-thrown immediately. Also, it no longer attempts to send to its targets more than once. Thus, the 'rejectionLimit' and 'retryInterval' properties have been removed. The retry behavior actually belongs in an interceptor/template on a per-MessageTarget basis. Some targets are retry-able (e.g. might throw a RemoteAccessException), but others are not. Therefore, the SimpleDispatcher should not have this awareness; such configuration options belong with the individual target instead (part of INT-337).
2008-08-18 19:36:04 +00:00
.classpath
Upgraded to Spring 2.5.5.A (INT-336).
2008-08-14 19:58:32 +00:00
.project
Updated the names of the projects
2008-05-20 21:41:01 +00:00
build.xml
Updated the names of the projects
2008-05-20 21:41:01 +00:00
ivy.xml
Upgraded to Spring 2.5.5.A (INT-336).
2008-08-14 19:58:32 +00:00
template.mf
Updated manifest templates for Spring 2.5.5.A
2008-08-14 20:21:58 +00:00