Hi,

Just a thought crossing my mind...

I need a customized JMS DestinationResolver, but I would like the elements to be cached, to avoid reinstantiating new Queue objets every time.

I have noticed the interface CachingDestinationResolver with one implementation JndiDestinationResolver.
Would it make sense to have in Spring Integration a class AbstractCachingDestinationResolver so that all sub-classes don't have to reimplement the cache mechanism?

Thanks!

Pierre