I have finished introducing the support for ContainerMonitoring which
is the default monitoring configuration that any container or
appserver part can use to set the monitoring level. In the process I
removed bunch of MonitoringItem subclasses that became unnecessary as
these containers will now use the new ContainerMonitoring interface
only.
I also removed the upgrade code that was added to change our old
monitoring configuration data to these defunct MonitoringItem
subclasses. This was I believe causing the startup regression we
experienced in the last promotion build.
So there are 2 ways to have monitoring configuration for your
component, you can use the ContainerMonitoring and have the basic
level setting capability, nothing else to do, the monitoring framework
will take care of changing the levels upon certain asadmin commands
etc...
You can also have a more sophisticated monitoring configuration, by
subclassing the MonitoringItem. In such case, you will be responsible
for providing asdmin commands and set the appropriate levels on the
monitoring framework yourself (set of APIs to do that being worked on
right now).