Then you'll have a problem. I guess there are 3 solutions. 1) Make the plugins mbeans (or xmbeans) themselves, so you can create them using any constructor (the -service.xml syntax permits this). Then make the central mbean have a dependency list with their ObjectNames:
| <mbean code="myBean" name="domain:name=x"> | <depends-list optional-attribute-name="ObjectNameList"> | <depends-list-element>domain:name=y</depends-list-element> | <depends-list-element>domain:name=z</depends-list-element> | </depends-list> | </mbean> | This has the advantage of the plugins being manageable as well. 2) Have an attribute of type org.w3c.dom.Element that supports your own arbitrary format for specifying classes and constructors parameters. You'll then have to parce that dom Element and do whatever (instantiate and initialize the mbean. As an example see how the SubscriptionList attribute is parsed in class org.jboss.system.ListenerServiceMBeanSupport, or look at how org.jboss.system.ServiceConfiguration is implemented. 3) Wait a few months for the new JBoss MicroContainer that will let you do (1) but without actually the mbean requirement. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881686#3881686 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881686 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
