[ https://issues.jboss.org/browse/WFCORE-2042?page=com.atlassian.jira.plugi... ] Michal Petrov commented on WFCORE-2042: --------------------------------------- [~gaol], [~brian.stansberry] I'm going to comment here for both issues. From what I'm seeing the problem is that the filter cannot be applied to nested attributes. I think a good solution would be having another attribute in the query operation for filtering on otherwise non-addressable resource (i.e. the "where" functionality wouldn't need to change, at least for the given examples). The obvious choice is to call it "from", [I've implemented the basics|https://github.com/michpetrov/wildfly-core/commit/3ece8247ed7fcd75...]; the operations would then look like this: {code} /subsystem=security/security-domain=*/authentication=*:query(from=login-modules, where={code=RealmDirect}) { "outcome" => "success", "result" => [{ "address" => [ ("subsystem" => "security"), ("security-domain" => "other"), ("authentication" => "classic") ], "outcome" => "success", "result" => [{ "code" => "RealmDirect", "flag" => "required", "module" => undefined, "module-options" => {"password-stacking" => "useFirstPass"} }] }] } {code} and for WFCORE-2041: {code} /core-service=capability-registry:query(from=possible-capabilities,where={name=org.wildfly.data-source}) { "outcome" => "success", "result" => [{ "name" => "org.wildfly.data-source", "dynamic" => true, "registration-points" => [ "/subsystem=datasources/data-source=*", "/subsystem=datasources/xa-data-source=*" ] }] } {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)