Dependencies based on service events
------------------------------------
Key: JBMICROCONT-2
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-2
Project: JBoss MicroContainer
Type: Feature Request
Reporter: Scott M Stark
The current state based dependency mechanism does not allow for dependencies on
service specific events. Such a dependency is really a dependency on a service
specific state change that happens to be signalled by a jmx notification for
example. A common scenario is service A waiting for the initial startup of the
jboss server as indicated by a jmx notification. This can be expanded to a
service B which needs to know when service A has completed its post jboss
server startup activity. Since service may not be explicitly coded with state
machines in mind, it would be good if the container framework allowed for an
externalized description of an extended state machine with the new states
beyond the normal service lifecycle described in terms of the events that
result in the exteneded state transitions (jmx events, method invocations,
etc.). Dependencies on the extended state diagram could then be expressed.
Certainly a service should be able to manifestly describe its extended state
diagram as part of its deployment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
