[
https://issues.jboss.org/browse/WFCORE-2042?page=com.atlassian.jira.plugi...
]
Lin Gao commented on WFCORE-2042:
---------------------------------
Thanks Michal for the comments, adding the +from+ parameter maybe an option, but it may
confuse the user because we have the +select+ parameter which sounds similar.
I think it would be better to solve the problem that the filter cannot be applied to
nested attributes instead of adding more parameters.
The dot notation may be used to split parent and sub resources, the wildcard notion may be
used to apply for filtering on multiple resources(like Brian's comment above).
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
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)