Hi Scott,
Our deployments generally boil down to a classpath
and a set of mbeans.
There is also a contract to define a directed graph
across deployments which orders the mbean lifecycle
invocations using depends
There are also implicit rules like:
1) deployments wait for their deployer
2)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Adrian Brock
Sent: Monday, February 02, 2004 5:19 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Expansion of service dependencies to
redeployment
Hi Scott,
Our deployments generally boil down
So a user has a scenario that could
M1 -Pa- M4 -Pd- |
*
M2 -Pc- M5 -Pd- M7
*
M3 -Pb- M6 -Pe- |
Px = protocol x with seperate contract_x.jar for interfaces
Mn = mbean n that depends on one or more protocols
whenever a protocol contract jar for which
