> -----Original Message----- > Aaron, > > I agree with you about the container extensions. I'm currently thinking of > adding JMX support to Merlin. While I can have a lifecycle extension > automatically register specific components (components that implement the > Manageable interface for example) as MBean in an avalonized MBeanServer, I > would like to dynamically instrument these components (ie build their > associated MBean) based on component meta-data. For example, we could have > a > specific management section within a xinfo file (I don't know, maybe this > is > already the case in Phoenix ?) describing the management interface with > the > constructor / operations / attributes / notifications the component want > to > expose it its management view (tags could be used to generate the > management > part of the descriptor). An (easy ?) way to have something running would > be > to use the Commons Modeler and have it build ModelMBean for each > Manageable > component based on reflection / deployment descriptor.
Laurent, I'm interested in seeing what you have in store for the JMX adaptor. I'm putting together some patches for the assembly package which may provide the sort of extension you're looking for (I'd like it for some JNDI and JMS extensions). It'd be similar to what I wrote in the "[RT] Container Components" thread today. You'd get access to the object and the associated Appliance info which should give you everything you need. Also, you may want to look at Jakarta Commons Modeler project which works with MBeans: http://jakarta.apache.org/commons/modeler.html jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
