----- Original Message -----
From: "Leo Simons" <[EMAIL PROTECTED]>
To: "Avalon Development" <[EMAIL PROTECTED]>
Sent: Wednesday, June 13, 2001 2:30 PM
Subject: RE: MBeanComponentManager ???
> > At 11:11 PM 6/12/01 -0600, Mircea Toma wrote:
> > >The ComponentManager will use internally a MBeanServer to lookup
MBean-s
> > >using role names which in this case will be the MBean's object
> > name. Also it
> > >uses the MBeanServer to manage Component/MBean lifecycle by calling
> > >mBeanServer.isInstaceOf(...) in order to learn what to do with it.
>
> I'm all for filling gaps in Java specs, but this sounds like a
> 'modification'
> which is probably not something we should do here at Apache. But that's
not
> my primary concern.
>
> Conceptually, the MBeanServer is there to expose a management interface
> to humans / console apps / cronjobs / init scripts / whatever. the JMX
> impl(s) are written to support this. When you use an MBeanSever as the
> component manager, you loose inversion of control (probably),
.....why??
> security
> (very likely) and what you will get is a lot of overhead for unused
> functionality.
...... I agree!
> The ComponentManager needs to be speedy, JMX isn't (doesn't have to be).
....yes, but it will be a distributed ComponentManager if the MBeanServer is
distributed.
>
> I think that what should be exposed for management (by phoenix) are
> ServerApplications. Finer graining is inappropriate here. And of course,
> life cycle management for those could be handled with a MBeanServer
> (something we've talked about but have yet to decide on).
>
> Finally, making the assumption {MBean object name} == {role name} may
> cause problems in some apps; it probably violates some framework contract.
.....then maybe the framework contracts are to tight!
>
> I may be wrong about this tho =)
>
> cheers,
>
> Leo
>
>
> ---------------------------------------------------------------------
> 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]
