Hi,
Your prototype is quite impressive as they can show both the configuration points & service points as MBeans.
But as your remark says, we need to find a way to expose the core service object as MBean because the core service object can have more attributes and operations than its interface. And we should be able to access all attributes of a service object defined in the hivemind.xml file, not just the ones defined by its interface.
I would suggest to add an attribute to the service point MBean and this attribute should store the ObjectName of the core service MBean. And we can navigate from the service point MBean to its core service MBean. In order to do this, we need to have Hivemind's support to get the core service object of a service. The ServicePoint interface will be the appropriate place to get the core service object. But this changes also involve the ServiceModel objects as the ServicePointImpl object gets the service from one of the ServiceModel. It becomes rather complicate for the pooled and threaded service model and I have NO ideas how to do that.
BTW, I have extended HiveMind (using AspectJ) to register the core service objects as MBean after their instantiation (only for the primitive & singleton service model). But this extension only works for the core services, it does not include its interceptors.
Eric
Achim Huegen wrote:
Hi,
I invested time in building jmx support into hivemind. Some documentation and links to a working prototype are available here: http://wiki.apache.org/jakarta-hivemind/JmxPreview
I'm interested in feedback especially about the 'metadata' support.
Bye Achim Huegen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
