You are viewing a plain text version of this content. The canonical link for it is here.
Posted to phoenix-dev@avalon.apache.org by Jim Alateras <ji...@intalio.com> on 2002/09/02 14:43:44 UTC
registering mbean with mbeanserver
I have upgraded to use the latest version of phoenix with MX4J. Once I add
an MBean to my application how do I register it with the MBean Server?
cheers
</jima>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: registering mbean with mbeanserver
Posted by Jim Alateras <ji...@intalio.com>.
thanks once again
> -----Original Message-----
> From: Peter Donald [mailto:peter@apache.org]
> Sent: Wednesday, September 04, 2002 9:36 PM
> To: Avalon-Phoenix Developers List
> Subject: Re: registering mbean with mbeanserver
>
>
> On Mon, 2 Sep 2002 22:43, Jim Alateras wrote:
> > I have upgraded to use the latest version of phoenix with MX4J.
> Once I add
> > an MBean to my application how do I register it with the MBean Server?
>
> The MBean server is not directly exposed to the blocks at this
> stage. In a few
> weeks we should have a mechanism via which you can expose objects to
> management system directly. However at the moment you have to do it the
> following way.
>
> * First you define your component as per usuall
> * Then you define an interface via which you want your block to
> be managed.
> And make your block implement this interface
> * then you place something like
>
> <!-- interfaces that may be exported to manange this block -->
> <management-access-points>
> <service name="com.biz.MyServiceMBean"/>
> </management-access-points>
>
> to your xinfo file. If you are autogenerating your xinfo file via
> xdoclet then
> you add something like the following to your class level javadoc
>
> @phoenix:mx name="com.biz.MyServiceMBean"
>
> This will expose a very raw MBean to the MBeanServer. If you want to add
> descriptions and prettier display names and all that jazz then
> you need to
> either hand write a mxinfo file (management extension file) but
> that is not
> recomended. It would be wiser to generate this file from xdoclet
> markup in
> file. Download latest phoenix and look in the docs to see how it works (I
> think the docs are prefixed with guide-mx-*). The docs are mostly
> done but I
> believe Huw was going to touch it up before release. Look in the
> o.a.a.phoenix.interfaces.* package for examples of interfaces marked up.
>
> I believe it is also possible to just markup Blocks to expose
> management info
> though not sure about that.
>
> --
> Cheers,
>
> Peter Donald
> ---------------------------------------------------
> Murphy's law - "Anything that can go wrong, will."
> (Actually, this is Finagle's law, which in itself
> shows that Finagle was right.)
> ---------------------------------------------------
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: registering mbean with mbeanserver
Posted by Peter Donald <pe...@apache.org>.
On Mon, 2 Sep 2002 22:43, Jim Alateras wrote:
> I have upgraded to use the latest version of phoenix with MX4J. Once I add
> an MBean to my application how do I register it with the MBean Server?
The MBean server is not directly exposed to the blocks at this stage. In a few
weeks we should have a mechanism via which you can expose objects to
management system directly. However at the moment you have to do it the
following way.
* First you define your component as per usuall
* Then you define an interface via which you want your block to be managed.
And make your block implement this interface
* then you place something like
<!-- interfaces that may be exported to manange this block -->
<management-access-points>
<service name="com.biz.MyServiceMBean"/>
</management-access-points>
to your xinfo file. If you are autogenerating your xinfo file via xdoclet then
you add something like the following to your class level javadoc
@phoenix:mx name="com.biz.MyServiceMBean"
This will expose a very raw MBean to the MBeanServer. If you want to add
descriptions and prettier display names and all that jazz then you need to
either hand write a mxinfo file (management extension file) but that is not
recomended. It would be wiser to generate this file from xdoclet markup in
file. Download latest phoenix and look in the docs to see how it works (I
think the docs are prefixed with guide-mx-*). The docs are mostly done but I
believe Huw was going to touch it up before release. Look in the
o.a.a.phoenix.interfaces.* package for examples of interfaces marked up.
I believe it is also possible to just markup Blocks to expose management info
though not sure about that.
--
Cheers,
Peter Donald
---------------------------------------------------
Murphy's law - "Anything that can go wrong, will."
(Actually, this is Finagle's law, which in itself
shows that Finagle was right.)
---------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>