Hi,

I have finished a first version of a service that exposes a Qi4j app in JMX automatically, giving you an opportunity to inspec the app much as you would with the Envisage tool. Attached is a screenshot showing what it looks like for the JMXTest in qi4j-lib-jmx.

What I'd like to do now is to put the configuration for the service, or any other related MBeans, in the same spot. The problem is that it's non-trivial for other JMX exporters to figure out the base ObjectName. In the shown screenshow I want the TestService Configuration to be a child of the TestService node, rather than all on its own. If I add a CircuitBreaker (or any other related MBean) it should also show up under the TestService rather than on its own.

At first I thought I could put the ObjectName from the export into the meta-info of the service, and others could look it up. But no such luck since meta-info is read-only.

So another idea is to have this be built-in to Qi4j, i.e. let Qi4j set the ObjectName for the artifact, so that it can be accessed using .metaInfo(ObjectName.class). The JMX exporter service would still do the actual exporting, just not figuring out how to build the name for it.

Does that sound ok? Any other solutions you can think of?

/Rickard

<<attachment: Screen shot 2010-12-03 at 13.01.21.png>>

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to