> > Some things have mbeans that really don't need configuration, just > lifecycle services. These are good candidates for the current sar > structure. TransactionManager comes to mind. Switch tm's with no code > bloat just by changing jbosstm.sar to tyrextm.sar. >
It is important to note that several MBeans rely on presence of java:/TransactionManager in JNDI without declaring explicit dependency on the existence of TransactionManagerMBean (at the very least, it is the MQ and ContainerFactory). Also, there is another more subtle dependency where the JRMPInvokerMBean depends on TransactionPropagationContext(Importer|Factory) to be present in JNDI. This is tricky because the JBossTM registers these in TransactionManagerMBean while in my new version of Tyrex plugin (not in CVS yet, it is still being tested) these are registered in JNDI by another MBean. So given the present state of dependency tracking, there is no way of expressing this dependency to satisfy both scenarios. Ideally, there should be a way of expressing dependency on presence of objects in JNDI and the MBeans that register themselves into JNDI should state that in the service.xml (i.e. under which names they register themselves). Anatoly. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
