Everything annotated in com.sun.enterprise.config.serverbeans should
work (a few items are not, I'm not sure what they are just yet).
Even better --
AMX now supports *any* ConfigBean that is annotated with
@AMXConfigInfo -- no a-priori knowledge is needed eg it's completely
"pluggable" by any module that has configuration. Before, AMX require
"Impl" classes population of various internal tables; that is no
longer the case. As part of that the 300ms or so class-loading delay
for the AMX interfaces is gone, never to return.
Lloyd
On Feb 26, 2008, at 1:52 PM, Kedar Mhaswade wrote:
> Super!
>
> I am assuming that the support is available for "all the configs"
> should there be more in the domain.xml.
>
> That's needed for a cluster-configuration although it is not a TP-2
> requirement.
>
> Lloyd L Chambers wrote:
>> A summary of AMX MBeans as of Tuesday 13:30 PST:
>> - AMX utility MBeans are all in place: DomainRoot, QueryMgr,
>> BulkAccess, etc
>> - AMX Config MBeans are present, but are currently *non-mutable*
>> (can't change attribute or property values). Nor can new config
>> elements be created. Supporting mutable attributes requires some
>> new code with the transaction support. That will come next, then
>> the ability to create new elements.
>> - A server restart is required to make the loaded MBeans match the
>> config file. There is no callback mechanism as yet in HK2 to let
>> AMX know when a ConfigBean goes way (yet)
>> - See below for which MBeans can be expected in a default
>> configuration as well as a dump of all Attributes. There are no
>> missing config MBeans AFAIK.
>> - No monitoring or JSR 77 MBeans are present as yet.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc