avalon-phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: Management MBean Interfaces - Stay or go?
Date Tue, 06 Aug 2002 06:05:26 GMT
Huw,

In effect you are suggesting that we need not bother with interfaces 
suffixed with MBean?  You are saying that with markup tags only, you can 
generate dynamically a JMX presence for a Phoenix hosted app?

I'm all for that, if true.  By code breakage you mean, through 
avalon-apps etc?

- Paul

> There are two ways to expose management information now:
>
> 1) use the phoenix-mx tags to markup blocks/apps/components as 
> management-enabled and then specify the methods and attributes to export
> 2) have the class implement a management interface (usually called 
> *MBean), and pass that into the export() method
>
> Method 2) is supported, but at least in my opinion, no longer the best 
> way to go.  Can I remove them and then mark-up the base classes with 
> the management info?  Or will that break a lot of code?
>
> If its a problem, I can markup the MBean interfaces instead.  The 
> result is the same, I just think less classes is better if we can get 
> there.
>
> - Huw
>
>
> --
> To unsubscribe, e-mail:   
> <mailto:avalon-phoenix-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:avalon-phoenix-dev-help@jakarta.apache.org>
>
>
>




--
To unsubscribe, e-mail:   <mailto:avalon-phoenix-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-phoenix-dev-help@jakarta.apache.org>


Mime
View raw message