Interface for modeler MBeans.
This is the main entry point into modeler. It provides methods to create
and manipulate model mbeans and simplify their use.
Starting with version 1.1, this is no longer a singleton and the static
methods are strongly deprecated. In a container environment we can expect
different applications to use different registries.
Register a bean by creating a modeler mbean and adding it to the
If metadata is not loaded, we'll look up and read a file named
"mbeans-descriptors.ser" or "mbeans-descriptors.xml" in the same package
If the bean is an instance of DynamicMBean. it's metadata will be converted
to a model mbean and we'll wrap it - so modeler services will be supported
If the metadata is still not found, introspection will be used to extract
If an mbean is already registered under this name, it'll be first
If the component implements MBeanRegistration, the methods will be called.
If the method has a method "setRegistry" that takes a RegistryMBean as
parameter, it'll be called with the current registry.
bean - Object to be registered
oname - Name used for registration
type - The type of the mbean, as declared in mbeans-descriptors. If
null, the name of the class will be used. This can be used as a hint or
java.lang.Exception - Error registering MBean
void unregisterComponent(java.lang.String oname)
Unregister a component. We'll first check if it is registered,
and mask all errors. This is mostly a helper.
oname - The name used by the bean
int getId(java.lang.String domain,
Return an int ID for faster access. Will be used for notifications
and for other operations we want to optimize.
domain - Namespace
name - Type of the notification
An unique id for the domain:name combination
Reset all metadata cached by this registry. Should be called
to support reloading. Existing mbeans will not be affected or modified.
It will be called automatically if the Registry is unregistered.