Yes Peter. That gives me a pretty good idea. Thank you very much. Atul.
-----Original Message----- From: Peter Donald [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 2:58 AM To: Avalon framework users Subject: Re: JMX support in Phoenix Hi, At 11:52 AM 7/1/2002 -0700, you wrote: >I have a simple question. What do I have to do if I want to create a Phoenix >block to expose some monitoring parameters through the JMX interfaces. You create a java interface that implements your management interface. By custom it is often the name of the block (or service) with the post fix "MBean". ie Implementation Class: com.biz.MyBlockImpl Service Interface: com.biz.MyService Management Service Interface: com.biz.MyServiceMBean Then you create a section in your block info file that looks like <management-access-points> <service name="com.biz.MyServiceMBean"/> </management-access-points> Alternatively if you are using xdoclet to generate your .xinfo files then you use a tag at the top of your class that looks like @phoenix:mx name="com.biz.MyServiceMBean" Then when you deeploy this bean it will be exported to MBeanServer (if phoenix is built with JMX support). Does that answer your question? Cheers, Peter Donald ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "Faced with the choice between changing one's mind, and proving that there is no need to do so - almost everyone gets busy on the proof." - John Kenneth Galbraith ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
