The solution is not yet very well defined. Right now catalina can be extended with Valves or connectors or listeners. Some of them (like jk connector ) can define MBeans. The major problem is having the admin interface recognize them - it should work but I never tried.
I already committed some code to modeler to allow modules to have their own modeler description ( in META-INF/modeler-mbean.xml ) and have it loaded automatically using getResources(). The code is not yet used, but will probably be for 5.0 ( or I hope so ). But if you implement your own mbean - you can register them yourself. The only important thing is to get the MBeanServer using the same mechanisms ( i.e. get existing instead of creating new one ). Also note that there are discussions on using modeler mbean to implement config changes ( it is not yet clear what's the best solution ), that may affect the support for custom mbeans. Another issue that wasn't much discussed is having mechanisms to use mbeans as extensions ( hooks, etc) - and use the mbean lifecycle and naming as a registration ( or alternatively, use a JNDI/JMX combination - the big problem with JMX is that you can't get the real object, all calls must be made via mbean server) Costin Jakob Praher wrote: > hi all, > > first of all kudos for the 4.1.x release - working with jmx is simply > great ;-) > > I have a question, how to best extend catalina through jmx: > > for instance I have a special connector mbean or adaptor mbean, that I > want to load into catalina. > > is there a way (for instance in the server.xml configuration file) to > laod this mbean during startup ? > > if not: what is the best way to plug in a third party mbean into > catalina ? > > should I write a custom lifecyclelistener? > > thanks > > -- Jakob > "the best way to predict the future ist to invent it" -- Alan Kay -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
