Re: [infinispan-dev] Obtaining cache via CDI on WildFly

Gunnar, While WF doesn't include infinispan-cdi integration, you can inject Infinispan caches defined within the Infinispan subsystem as standard EE resources via the their JNDI bindings. This approach has the advantage of container-managed lifecycle of the cache, even when referenced by multiple deployments. e.g. @Resource(lookup = "java:jboss/infinispan/cache/foo/bar") private Cache<?, ?> cache; // References the "bar" cache of the "foo" cache container or @Resource(lookup = "java:jboss/infinispan/cache/foo/default") private Cache<?, ?> cache; // References the default cache of the "foo" cache container Unfortunately, a long standing weld integration bug prevents @Resource lookups from working correctly when the containing class is instrumented by CDI. To workaround this, move the JNDI lookup to a <resource-ref/> or <resource-env-ref/> in your deployment descriptor and reference your cache resource via its reference name. e.g. <resource-env-ref> <resource-env-ref-name>my-cache<resource-env-ref-name> <resource-env-ref-type>org.infinispan.Cache<resource-env-ref-type> <lookup-name>java:jboss/infinispan/cache/foo/bar</lookup-name> </resource-env-ref> @Resource(name = "my-cache") private Cache<?, ?> cache; Paul On Wed, Dec 5, 2018 at 3:47 AM Gunnar Morling <gunnar(a)hibernate.org&gt; wrote: