Steve, Thanks for the timely response. I will look into the two options described below early next week. My understanding is that this will enable me to declare JMX access points to my components. Can you clarify whether I need to write the code that will register these points with the MBeanServer or does this code exist already....i suspect the former
cheers </jima> > -----Original Message----- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: Friday, 26 September 2003 12:43 PM > To: Avalon Developers List > Subject: Re: [merlin] jmx support > > > > > Jim Alateras wrote: > > >Is there anything in Merlin today that parallels JMX support in > >Phoenix, in particular the use of .mxinfo files to declare a > >component's JMX interface > > > > No. > > JMX support in Merlin is ... "preliminary". You can startup > merlin as a > jmx server and via a jmx client invoke shutdown and > redeployment. This > works just fine. The jmx related strategy covers three areas > - (a) how > to automate internal jmx handling of appliances (managers of > component > types) so that componet types become auto-managed relative to Avalon > lifecycle interfaces, and (b) how to handle support for custom > management interfaces, and (c) how to federate multiple > merlin kernels > via adapters to a single jmx server management point. > > In the first area there are some preliminary resources in > place but it > is largely testing phase at this time. The second area - > which is the > subject your concerned about can be addressed two ways: > > (a) use the existing phoenix source code and build into merlin the > equivalent functionality > (b) use the qdox jmx solution with @jmx tags > > Either direction presents a few problems. Using the qdox solution we > run into problems with their maven plugin which appears to be doing a > really strage bunch of things that at the end of the day are not > required - but their ant task works fine. Taking this approach would > require that we write a maven plugin for the qdox jmx tag > handler. But > it would be better if the guys from Qdox did this! Going the phoenix > style means replicating content that will probably (?) come > from qdox. > > At the end of the day we need a jmx plugin for maven and from the > artifacts generated, we need merlin to register and > dererigister those > management access points as required. > > Cheers, Steve. > > -- > > Stephen J. McConnell > mailto:[EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
