Skip to content

DATACMNS-69 Updated cache key to bean name rather than class #9

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

DATACMNS-69 Updated cache key to bean name rather than class #9

wants to merge 1 commit into from

Conversation

@philwebb
Copy link
Member

@philwebb philwebb commented Sep 1, 2011

No description provided.

@odrotbohm
Copy link
Member

Good catch! Applied your patch but switched back to the cache.containsKey(…) approach as otherwise we would constantly retry to resolve a class if it had previously failed. So putting null into the cache actually means: we've tried but failed to resolve the type, so we don't actually have to retry again.
@odrotbohm odrotbohm closed this Sep 1, 2011
Aloren pushed a commit to Aloren/spring-data-commons that referenced this pull request Jun 20, 2019
@spencergibb
Create a ServiceRegistry interface.
bf4b6e3 
Allow service discovery systems to register more than one instance. Automatic registration will still take place. Add boolean autoRegister() to EnableDiscoveryClient, defaults to true. Add ServiceRegistryEndpoint. fixes spring-projectsgh-9
@spring-projects-issues spring-projects-issues mentioned this pull request Dec 30, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants

@philwebb @odrotbohm