Thanks Amy !
That was my initial understanding.
The problem is that the ModelMBean implementation in JMX-RI and MX4J
don't seem to behave this way, and the spec wording is ( page 84 in the
1.1 PDF ):
I believe ModelMBean implementation in JMX-RI and MX4J behave this way for
all external
Amy Roh wrote:
The problem is that the ModelMBean implementation in JMX-RI and MX4J
don't seem to behave this way, and the spec wording is ( page 84 in the
1.1 PDF ):
I believe ModelMBean implementation in JMX-RI and MX4J behave this way for
all external Notification listeners.
Not sure
Craig, Amy - or anyone who knows JMX, I need help :-)
I just can't find any way to add an attribute change listener
in the whole JMX spec, unless I have the instance of the model
mbean. And there is no way to get that instance.
All query and get methods in MBeanServer return ObjectInstance -
More info:
I checked MX4J, JMX-RI and JBoss. The model mbean implementations
in the first 2 are consistent - and do not send attribute change
notifications on the 'normal' listeners ( those registered with
addNotificationListener). That's also consistent with the spec
wording all other
Costin,
Costin Manolache wrote:
Craig, Amy - or anyone who knows JMX, I need help :-)
I just can't find any way to add an attribute change listener
in the whole JMX spec, unless I have the instance of the model
mbean. And there is no way to get that instance.
I talked to Hans Hrasna in JMX
Thanks Amy !
That was my initial understanding.
The problem is that the ModelMBean implementation in JMX-RI and MX4J
don't seem to behave this way, and the spec wording is ( page 84 in the
1.1 PDF ):
In the model MBean, AttributeChangeNotifications are sent to a separate
set of listeners
