[Openjmx-devel] FW: ModelMBeans, implemented interfaces and management interfaces

[Bordet, Simone]

Roger, I'm taking care of your problems...
let's see what is the answer.

Simon

-----Original Message-----
From: Bordet, Simone
Sent: venerdì 25 gennaio 2002 10:19
Subject: ModelMBeans, implemented interfaces and
management interfaces
Hi all,
ModelMBean interface extends, among others, PersistentMBean.
Is this call legal ?
ObjectName name = ...;
MBeanServer server = ...;
server.invoke(name, "store", new Object[0], new String[0]);
Method store is implemented by ModelMBeans, but should it be
part of the management interface exposed by the MBeanServer ?
And along with the possibility to invoke it, should also be
part of the ModelMBeanInfo metadata ?
At beginning I thought yes, but ModelMBean implements also
NotificationBroadcaster, so if the above is true, also these
server.invoke(name, "addNotificationListener", ..., ...);
server.getAttribute(name, "NotificationInfo");
but this seemed to me "violating" the fact that the
MBeanServer is responsible for adding/removing listeners, for example.
server.invoke(name, "setManagedResource", ..., ...); or from
server.setAttribute(name, new Attribute("ModelMBeanInfo", ...));
Should they be allowed ?
when a DynamicMBean is implementing some other interface,
should the methods of these interfaces be automatically
required to be in the management interface (and thus in the
MBeanInfo metadata), it's facultative, or it's forbidden ?
I was thinking also to the implementor of a DynamicMBean that
is also a NotificationBroadcaster: should the implementor be
forced to expose in the management interface methods of the
NotificationBroadcaster interface ?
Thanks
Simone Bordet
Professional Services, Java Engineer
Compaq Computer, Italy