Thanks Sahoo.
GlassFish V3 *will* have JSR 77 support, but not there yet. The
pointer Sahoo supplied to AMX is for V2; in V3 the AMX MBeans are an
open system:
https://glassfish.dev.java.net/nonav/v3/admin/planning/V3Changes/V3_AMX_SPI.html
Any MBean may of course be loaded into the V3 runtime, but MBeans that
conform to the AMX specification will be more useful in terms of
consistency, and management support.
Lloyd
..............................................
Lloyd Chambers
GlassFish team, LSARC member
On Feb 24, 2009, at 3:47 AM, Sahoo wrote:
> Miro,
>
> GlassFish supports JSR-77 [1]. In addition to those management
> functions, GlassFish has a rich management API implemented using
> JMX. It is called AppServer Management Extension (AMX) [2]. We have
> not thought about integration of RFC-139 with GlassFish. My
> thinking is when the underlying OSGi platform supports it, it will
> be automatocally exposed to end user. There are some JMX mbeans
> implemented in Felix, but I don't think they have been released yet
> and I don't know how long it will take for Felix to implement
> RFC-139. What exactly are you looking for?
>
> Thanks,
> Sahoo
>
> [1] J2EE Management Spec: http://jcp.org/en/jsr/detail?id=77
> [2] https://glassfish.dev.java.net/javaee5/amx/
>
> Miroslav Nachev wrote:
>> Hi,
>>
>> What about the management process (deploy, undeploy, start, stop,
>> logging, debug, monitoring, etc.) in GlassFish and the OSGi
>> specification for management (RFC-139)? Will be used or not?
>>
>>
>> Miro.