In RHQ 3.x I had the following in my rhq-plugin.xml:
<service name="xxx" description="xxx" discovery="org.rhq.plugins.jmx.MBeanResourceDiscoveryComponent" class="org.rhq.plugins.jmx.MBeanResourceComponent" singleton="true">
<runs-inside>
<parent-resource-type name="JMX Server" plugin="JMX"/>
</runs-inside>
<plugin-configuration>
<c:simple-property name="objectName" default="xxx" readOnly="true"/>
<c:simple-property name="nameTemplate" default="xxx"/>
</plugin-configuration>
<service name="yyy" description="yyy" discovery="org.rhq.plugins.jmx.MBeanResourceDiscoveryComponent" class="tv.seachange.monitoring.plugins.utils.SeachangeMBeanResourceComponent" singleton="true">
<plugin-configuration>
<c:simple-property name="objectName" default="yyy" readOnly="true"/>
<c:simple-property name="nameTemplate" default="yyy"/>
</plugin-configuration>
<metric property="yyy" displayName="yyy" dataType="trait" defaultOn="true" category="performance" description="yyy"/>
</service>
...
</service>
This would nest service yyy under xxx. However, in 4.7 only top level services seem to connect and grab attributes. Is there another way to accomplish this nesting?
