Hi,
When Marc put in the new classloading stuff for 3.0, he had each mbean
being configured, inited, and started individually (although in the order
of the *service.xml file).
David Maplesden added some package depending on mbean dependency control
and changed the config/init/start to do each step to the entire deployment
unit (as it is in 2.4).
I am in the process of making the dependencies operate on an mbean to mbean
level by means of mbean references and would like to change this process
back to config/init/start mbean by mbean.
Given mbean to mbean dependencies, will this cause any problems? Please
give a specific example. I didn't catch David M's example when he made the
first change.
Heres an example of the mbean references/ dependencies at work:
<mbean code="org.jboss.test.jmx.mbeanconfigure.TestMBeanA"
name="test:name=TestMBeanA">
<mbean-ref name="Mbeanb">test:name=TestMBeanB</mbean-ref><!--ObjectName
valued attribute get/setMbeanb-->
<mbean-ref-list name="Mbeans"> <!--list valued attribute, elements are
ObjectNames-->
<mbean-ref-list-element>test:name=TestMBeanB</mbean-ref-list-element>
<mbean-ref-list-element>JBOSS-SYSTEM:service=TransactionManager</mbean-ref-list-element>
</mbean-ref-list>
</mbean>
<!--TestMBeanA will be suspended waiting for TestMBeanB when it is first
deployed -->
<mbean code="org.jboss.test.jmx.mbeanconfigure.TestMBeanB"
name="test:name=TestMBeanB">
<mbean-ref name="Mbeana">test:name=TestMBeanA</mbean-ref>
</mbean>
<!-- TestMBeanB will find TestMBeanA, so it can deploy completely. Once it
is started, its dependencies are checked, allowing (if the tm is present!)
TestMBeanA to finish deploying -->
Suggestions for better element names will be appreciated.
I am planning to use these two new elements in the mbean element because
they have such different semantics than the existing attribute element.
Thanks!
David Jencks
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
