[
https://issues.jboss.org/browse/WFCORE-396?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFCORE-396:
-----------------------------------------
[~luck3y] I'm pretty sure I named it that deliberately. Granted the name is
questionable since "domain" can imply the entire domain not just a host, but I
don't think I did ti by mistake. I basically came up with two op names, one for a
single process request (resolve-expression) and this one for requests that will get rolled
out to multiple domain processes.
Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops
should be visible to users
---------------------------------------------------------------------------------------------
Key: WFCORE-396
URL:
https://issues.jboss.org/browse/WFCORE-396
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Ken Wills
Fix For: 3.0.0.Beta1
Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users
(e.g. in read-operation-names results etc) in order to not delude users into thinking they
can do something like :write-attribute directly on a server (instead of modifying host or
domain config elements.)
But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config
should be valid.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)