Details
-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
Description
The global query() operation works only for simple attributes like:
[standalone at localhost:9990 /] /subsystem=datasources/jdbc-driver=*:query(select=[driver-xa-datasource-class-name], where={driver-name=h2}) { "outcome" => "success", "result" => [{ "address" => [ ("subsystem" => "datasources"), ("jdbc-driver" => "h2") ], "outcome" => "success", "result" => {"driver-xa-datasource-class-name" => "org.h2.jdbcx.JdbcDataSource"} }] }
It would be good if the 'query()' operation can filter the resources by specifying value of attributes which are inside of the complex attribute, so that, for example, the following commands can work well as expected:
[standalone at localhost:9990 /] /core-service=capability-registry:query(select=[possible-capabilities],where={possible-capabilities.name=org.wildfly.data-source})
[standalone at localhost:9990 /] /deployment=batch-chunk.war/subsystem=jaxrs/rest-resource=*:query(select=["rest-resource-paths"], where={"rest-resource-paths.resource-path"=>"batch/jobs"})
The rest-resource-paths.resource-path and possible-capabilities.name in 'where' parameter are proposed attribute names in enhanced syntax, other options maybe possible too.
Attachments
Issue Links
- is related to
-
-
- Open
-