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

Allowed multiple named configurations for Infinispan client #26478

Closed
tristantarrant opened this issue Jun 30, 2022 · 3 comments · Fixed by #32494
Closed

Allowed multiple named configurations for Infinispan client #26478

tristantarrant opened this issue Jun 30, 2022 · 3 comments · Fixed by #32494
Assignees
Labels
area/infinispan Infinispan kind/enhancement New feature or request
Milestone

Comments

@tristantarrant
Copy link

Description

The current Infinispan extension only supports a single RemoteCacheManager. Ideally we should allow specifying multiple named configurations, using an annotation such as @InfinispanClientName.

// Inject the default client
@Inject
RemoteCacheManager remoteCacheManager;

// Inject the "other" client
@Inject @Remote("other")
RemoteCacheManager remoteCacheManager;
quarkus.infinispan-client.server-list=hotrod://host:11222
quarkus.infinispan-client.other.server-list=hotrod://host-other:11222

Implementation ideas

No response

@tristantarrant tristantarrant added the kind/enhancement New feature or request label Jun 30, 2022
@quarkus-bot quarkus-bot bot added the area/infinispan Infinispan label Jun 30, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented Jun 30, 2022

/cc @karesti, @wburns

@geoand
Copy link
Contributor

geoand commented Jul 1, 2022

We definitely want something like this. We do something similar for most of the other datasources.

@karesti
Copy link
Member

karesti commented Jul 16, 2022

@tristantarrant @geoand taking this point. https://issues.redhat.com/browse/ISPN-14012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infinispan Infinispan kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants