Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for caching destination resolver [SPR-11939] #16556

Closed
spring-projects-issues opened this issue Jul 1, 2014 · 2 comments
Closed

Add support for caching destination resolver [SPR-11939] #16556

spring-projects-issues opened this issue Jul 1, 2014 · 2 comments
Assignees
Labels
in: messaging type: enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jul 1, 2014

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

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jul 1, 2014

Agim Emruli commented

Pull request added

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jul 2, 2014

Juergen Hoeller commented

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).

Juergen

@spring-projects-issues spring-projects-issues added in: messaging type: enhancement labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.1 RC1 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants