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

CDI support can fail due to Set.toString() used as Map key [DATACOUCH-203] #515

spring-projects-issues opened this issue Feb 8, 2016 · 0 comments
in: repository type: bug


Copy link

@spring-projects-issues spring-projects-issues commented Feb 8, 2016

Mark Paluch opened DATACOUCH-203 and commented

Current CDI support can fail, because it stores CouchbaseOperations instances in a map with String key representing a set of Qualifiers:

couchbaseOperationsMap.put(bean.getQualifiers().toString(), ((Bean<CouchbaseOperations>) bean));

However, Set doesn't define iteration order (or even String representation for that matter), so with 2+ Qualifiers there's a good chance to get them in the wrong order and fail to find operations

Affects: 1.3.2 (Fowler SR2), 1.4.2 (Gosling SR2), 2.0 GA

Issue Links:

  • DATACASS-249 CDI support can fail due to Set.toString() used as Map key

Referenced from: pull request #108, and commits db4c24d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: repository type: bug
None yet

No branches or pull requests

1 participant