[
https://issues.jboss.org/browse/CDI-182?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-182:
--------------------------
Fix Version/s: TBD
(was: 1.1 (Proposed))
Affects Version/s: 1.1.EDR1
(was: 1.1 (Proposed))
I'm deferring this for now, as CDI makes no mention of how it should work in a cluster
at all, nor does Java EE really.
I would suggest raising this with your app server, and asking for them to add such events
as part of their extension API.
Cluster Lifecycle Events
------------------------
Key: CDI-182
URL:
https://issues.jboss.org/browse/CDI-182
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Events
Affects Versions: 1.1.EDR1
Environment: Any java environment.
Reporter: Kristoffer Sjögren
Priority: Minor
Fix For: TBD
CDI 1.1 defines a set of lifecycle events related to different context
within the application. We see a need to also define cluster lifecycle
events for applications.
These events could, for example, be used for subscribing/allocating
and unsubscribing/deallocating external services/resources.
More specifically, a @Cluster event that gets fired when an
application gets @Initialized in the cluster, that is, post
@Application @Initialized. And another @Cluster event that gets fired
when the application get @Destroyed in the cluster, that is, pre
@Application @Destroyed. These events only fires once per application
and cluster, independent on how many cluster instances exists.
Events are fault tolerant meaning that events are not affected by
failing instances going out-of-service, as long as the cluster is
still working. Notice that the @Destroyed event is of course only
invoked if the cluster terminates gracefully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira