[
https://issues.jboss.org/browse/WFLY-4562?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on WFLY-4562:
------------------------------------
[~sflanigan] To answer your original question - use a <resource-ref/> or
<resource-env-ref/>. This serves 2 purposes:
# Allows you to lookup the resource from a standard namespace (e.g. java:comp/env).
# Ensures the component lifecycle is bound to your bean.
[~xxd] @Resource injection _should_ ensure that the resource is started - although I have
seen reports that this isn't happening for CDI beans. Can you file jira for this?
Deprecate Infinispan container/cache start mode
-----------------------------------------------
Key: WFLY-4562
URL:
https://issues.jboss.org/browse/WFLY-4562
Project: WildFly
Issue Type: Enhancement
Components: Clustering
Affects Versions: 9.0.0.Beta2
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 9.0.0.CR1
start="EAGER" was only added to the Infinispan subsystem for use by JDG - so
that a given container or cache service would install as ACTIVE rather than ON_DEMAND. In
the context of WildFly, we would never want this since the modules referenced by cache
entries may not yet be loaded. Many users configure start="EAGER" and
inevitably have issues during redeploy. Consequently, we should drop this from the
subsystem XSD altogether and deprecate it from the model.
Effectively, only start="LAZY" will be supported.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)