Resolving destinations might expensive under some circumstances. Therefore it would be handy to have a caching destination resolver to be used along with the messaging module.
I've introduced this in a slightly revised form: as a CachingDestinationResolverProxy (allowing us to use the "CachingDestinationResolver" name for a potential future interface, along the lines of the same-named JMS support interface), with a bean-property-style configuration option, and no special handling of null results - since DestinationResolver isn't meant to ever return null (which I've made clearer in DestinationResolver's javadoc now).
Agim Emruli opened SPR-11939 and commented
Resolving destinations might expensive under some circumstances. Therefore it would be handy to have a caching destination resolver to be used along with the messaging module.
Affects: 4.0.5
Reference URL: #578
The text was updated successfully, but these errors were encountered: