Ok, so I looked through the code to see what was going on and I found that the
jboss.dependencies file is only controlling the startup of MBeans that register
with an object name of ":service=XXX", which is the pattern used by the
jboss ServiceMBeanSupport subclasses.
The DependencyManager does not run until after all MBeans have been loaded by
the JMX MLet service. Delaying the start of the jboss services to after the loading
of the MBeans seems inconsistent with the prescribed mechanism of an MBean
implementing the MBeanRegistration so that the bean can implement preRegister to:
Page 117 of the JMX spec:
"Get information about the environment, for instance, check on the existence of
services the MBean depends upon. When such required services are not
available, the MBean might either try to instantiate them, or raise a
ServiceNotFoundException exception."
I would suggest that the jboss main use two mlet files to allow for non-jboss MBeans
to assert dependecies on jboss services at a point at which the jboss services are
started. So, org.jboss.Main would:
1. Load jboss services from jboss.conf using the MLet service
2. Run the DependencyManager to start the services in the correct order
3. Load user services from a jboss-user.conf file using the MLet service.
Any objections to making this change?
----- Original Message -----
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Sunday, December 03, 2000 8:20 PM
Subject: [jBoss-User] Does the jboss.dependencies mechanism work?
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
