Just as a general comment, for the object name its good practice to have the type and name property and avoid any other additional properties in the object name.
Carsten 2013/8/14 Felix Meschberger <[email protected]> > > Am 14.08.2013 um 11:34 schrieb Bertrand Delacretaz: > > > On Wed, Aug 14, 2013 at 11:21 AM, Felix Meschberger <[email protected]> > wrote: > >> ...There is no such thing as a JMX Bean tree. Each JMX Bean has an > ObjectName and the only official > >> structuring is by the MBean's domain. The rest of name is just > name-value pairs... > > > > That's technically correct, but from the perspective of a jconsole > > user you see a tree, that's what I meant. > > JConsole is a presentation as is the Sling JMX ResourceProvider. > > What we are dealing with here are MBeans, and they don't care for nor know > of tree structures. Everything else would be crossing the abstraction > barrier. > > > > > The HC MBeans are currently registered under the > > org.apache.sling.healthcheck domain, and their service name and type > > names are configurable. Currently as a single string like > > "service/type", might be better to separate that in two separate > > properties. > > Yes. Leave the presentation to the presentation tools and care for the > correct and intended MBean mechanism > > Regards > Felix > > > > > -Bertrand > > -- Carsten Ziegeler [email protected]
