It doesn't look to me like the JMX RI solves our problem with load
order. I looked through the spec, and the relation service only seems to
operate on MBeans that already exist - the old chicken and egg problem.
On the other hand, it shouldn't be that hard to parse the
jboss.conf file ourselves, and manually invoke
server.createMBean(className, objectName) for each bean. Then we could
maintain the ordering in the conf file for when we start the beans.
Or perhaps better yet, we can just add another file with the
relationships we want, and load and parse that in order to determine the
appropriate startup order of the MBeans we have on hand. Then instead of
simply iterating through the Set returned by the MLet, we could select an
ordering ourselves based on the rules.
Hmmm... On the other hand, once we've created all the MBeans,
perhaps we could create Relations before we actually start them. But I
still don't see this working out. For one, we're the ones requesting
startup of each bean, so why bother with these complex relation structures
when we're just going to have to parse them ourselves to determine startup
order (and we could surely come up with something simpler). Additionally,
once we unload an MBean, its relations will presumably disappear since
according to me reading they can only operate on "live" MBeans.
I don't know - I guess the entire point of this "Relation" service
is passing me by. One good example would make a world of difference.
Aaron
