[
https://issues.jboss.org/browse/WFCORE-2042?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-2042:
------------------------------------------
I believe this one would require bringing a wildcard notion into the filter, as most
children have a dynamic element in their address and I expect filtering users, at least
sometimes, would want to match against all the children of a particular type.
That could be ok but we need to think through the semantics of where such a wildcard could
be allowed and whether that can be done in a way that makes sense for all uses of
'filter'.
Improve query operation for nested child resources
--------------------------------------------------
Key: WFCORE-2042
URL:
https://issues.jboss.org/browse/WFCORE-2042
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Lin Gao
Assignee: Brian Stansberry
This is another similar RFE as WFCORE-2041.
It would be good if the 'query()' operation can filter the resources by
specifying value of attributes which are +inside of nested child resources(not only by
the first level of child resource)+, so that, for example, the following command can work
well as expected:
{code:}
[standalone@localhost:9990 /] /subsystem=security:query(select=[security-domain],
where={security-domain.authentication.login-modules.code=RealmDirect})
{
"outcome" => "success",
"result" => undefined
}
// here the expected output are the security-domain resources which have the
loging-module RealmDirect defined.
{code}
The {{security-domain.authentication.login-modules.code}} in 'where' parameter is
proposed attribute name in enhanced syntax, other options maybe possible.
The different requirements between this WFCORE-2042 and WFCORE-2041 are:
* WFCORE-2041 focus on complex attributes in one management resource
* WFCORE-2042 focus on nested management resources with or without complex attributes
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)