This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

JMS: Abstract class for CachingDestinationResolver

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?