geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James deGraft-Johnson" <>
Subject RE: [services] getting service developers started - the initial component model
Date Tue, 12 Aug 2003 11:21:57 GMT

My understanding of the JMX/MBeans idea from SUN is so that it is possible
to create MBeans (Management Beans) as part of a J2EE application to support
administration, management and monitoring of the J2EE application. This is a
very powerful idea, which ideally will be supported by Geronimo.

The use of a JMX/MBeans model for Kernel framework shouldn't jeopardize the
above. In fact I assumed that the discussion of the MBeans as a service
component model was actually MBeans-like, i.e. basing the component model on
the MBeans design. (We can structure the Geronimo kernel like JMX without
actually making the kernel a JMX implementation, so as to incorporate into
the kernel the ability for J2EE application developers to create and install
actual MBeans.) Because of the above, this is what makes sense for this

James deGraft-Johnson
Software Engineer - IT
Verizon Information Services
Tel:         (240) 456-7018
Fax:        (240) 456-7072
Mobile:   (240) 475-1444 <>

-----Original Message-----
From: Alex Blewitt []
Sent: Tuesday, August 12, 2003 6:57 AM
Subject: Re: [services] getting service developers started - the initial
component model

> All that sounds reasonable and I fully agree with you. However, as the
> project is still in early stages I'd like to emphasize the fact that
> J2EE
> developers may want to deploy their own MBeans (doing things like
> flushing
> a cache) also at runtime. This possibility is without doubt been
> forgetten
> while WebLogic Server was coded. Even BEA WLS developers cannot supply
> one
> with any reasonable ways to deploy your own standard MBeans which do
> not
> have anything to do with WLS itself.

AFAIK the J2EE spec doesn't say anything about being able to put your
own MBean into a server. However, an MBean container for just this
purpose sounds like an excellent idea.

Note that I don't believe the server itself needs to be an MBean
container (in much the same way that the whole isn't a web container or
ejb container) but it seems reasonable to assume that at some future
point the J2EE spec may create the concept of an MBean container.

> Alex.

View raw message