One issue I'm considering for AMX ObjectNames is whether to include a
property in the ObjectName which categorizes the MBean eg "config",
"runtime", etc.
In V2 AMX had no such thing; ObjectNames were strictly limited only to
properties that made the ObjectName unique among others. However, the
"com.sun.appserv:" MBeans did have a "category" property.
Why add such a property? (And where does one stop?!). It can be
useful for selecting a subset of MBeans based on functionality eg "all
config MBeans".
WITHOUT: amx:j2eeType=X-DomainConfig,name=amx (Glassfish V2)
POSSIBLE: amx:j2eeType=X-DomainConfig,name=na,grp=config // possible
change, 'grp' = "group"
AMX MBeans already have a "Group" Attribute which does this, but one
cannot query ObjectNames based on MBean attributes. Note also that
the value of the j2eeType field is 100% consistent eg everything
ending in "Config" is a config MBean--but again, not actionable via
queryNames().
I'm inclined to stick with the V2 style even though a group or
category property is handy ('grp'). Comments welcome.
Lloyd
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc