affected hierarchical elemens: ".parent", ".child", ".grandparent" affected subexpressions: resourceConfiguration, pluginConfiguration, traits, availability for instance, if you say: "resource.parent.pluginConfiguration[princial] = admin" it should give you all resources that have a parent resource that has a plugin configuration property called 'principal' with the value admin it actually gives you all resources that have a plugin configuration property called 'principal' with the value admin
rev1746 - dynagroup support for ".child", ".parent", and ".grandparent" when using complex subexpressions such as ".pluginConfiguration", .resourceConfiguration", ".trait", and ".availability"
for testing i imported a single platform and created 4 different group definitions with one expression each: 1) resource.child.pluginConfiguration[princial] = admin 2) resource.pluginConfiguration[princial] = admin 3) resource.parent.pluginConfiguration[princial] = admin 4) resource.grandparent.pluginConfiguration[princial] = admin the expected results are: 1) the single platform resource 2) all auth-enabled JBAS (or EAP) instances 3) all resources that are direct children of the JBossAS Server type (ConnectionFactory, JBossMessaging, Datasource (2) JBossMQ, EJB3 Entity Tree Cache, Script, Embedded Tomcat Server, Web Application (WAR)) 4) all resources that are grandchildren of the JBossAS Server type (Connector, JBM JMS Topic, EJB3 Entity Tree Cache Interceptor, JMQ JMS Queue, JBM JMS Queue, VHost) for fuller coverage, the other subexpressions - ".resourceConfiguration", ".trait", and ".availability" - should be tested in a similar manner.
This requires a security enabled jbas instance.
All tests above work as described. rev2733
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-967