Read the book again. JMX only allows you to call methods on methods specified in the management interface. So you have to expose it or you have to get hold of an object reference but then you are outside JMX.
In JBoss we "missuse" JMX for an communication bus instead of the outside management. So you have the choice.
Have fun - Andy
I guess I should have been clearer.
I just didn't see how JBoss was achieving the communication within the JMX specification. The jboss
example (memory monitor) ran in isolation. It wasn't clear how you can utilize other jboss resources.
Again, I'm just a little confused as to how JBoss
makes available resources while claiming JMX as the
backbone for communication. Does this blur the separation
of management and non-management functionality?
<Does this blur the separation of management and non-management functionality>
Yes !!. In JBoss, most everything is done thru JMX. That is to say, it works like this:
Get a reference to MBean server. Then call the MBean server invoke method with the name of the object you want to call, the name of the method on that object, and the parameters to pass.