[
https://issues.jboss.org/browse/WFCORE-396?page=com.atlassian.jira.plugin...
]
Ken Wills edited comment on WFCORE-396 at 7/25/16 7:48 PM:
-----------------------------------------------------------
[~bstansberry]
https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m...
Is this "resolve-expression-on-domain" instead of
"resolve-expression-on-host" to reuse the descriptions or a typo? It seems like
a typo, since it shows up as resolve-expressions-on-domain in /host=xxx.
was (Author: luck3y):
[~bstansberry]
https://github.com/wildfly/wildfly-core/blob/master/host-controller/src/m...
Is this "resolve-expression-on-domain" instead of
"resolve-expression-on-host" to reuse the descriptions or a typo? It seems like
a type, since it shows up as resolve-expressions-on-domain in /host=xxx.
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)