Hi
I am not quite sure if there should be an order in the loading of the
MLets because the MLets should allow the user to load the MBeans
dynamically on demand. Therefore even when you have a load order in
your <MLET> definition it is useless when you want to reload or load
the MBean after the startup.
IMO the MBean should not rely on the load order but try to wait till
the necessary MBean(s) are loaded to connect to them (I think the
MBeanServer sends a Notification Event when a MBean is loaded).
Now register your MBean as a Notification Listener (you can use
NotificationFilter to reduce the number of events received) and then
wait till its registered (OK, Ok, of course only when the MBean(s) is
not already loaded).
You can make it even more advanced when you also listen to unregister
events of the MBean(s) you depend on to disconnect your MBean from the
other. Therefore a dynamic reload could be implemented and jBoss becomes
a real pluggable EJB Server.
Have fun
Mad Andy, good Pizza
> -----Original Message-----
> From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 30, 2000 5:27 AM
> To: jBoss Developer
> Subject: [jBoss-Dev] JMX Status?
>
>
> One of the things I just fought through to get the test beans to
> use Minerva was the JMX startup order issue. There's really
> no way around
> it without horrible hacks. Do we have any idea when the
> final JMX release
> will be available? I don't think we can call jBoss production-quality
> until we nail the startup order.
>
> Aaron
>
> P.S. I'm supposed to finally get a phone line on Friday, so I
> should be
> able to get internet access from home again soon! Woo-Hoo!
>
>
