[
https://issues.jboss.org/browse/WFCORE-421?page=com.atlassian.jira.plugin...
]
Jean-Francois Denise closed WFCORE-421.
---------------------------------------
Resolution: Won't Fix
The management model doesn't expose what are the operations one could call on non
existing / existing resources. As said in previous comment, "*" can be used
instead of bogus name.
cli tab-completion: filtering out operations not applicable to a
resource
-------------------------------------------------------------------------
Key: WFCORE-421
URL:
https://issues.jboss.org/browse/WFCORE-421
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Environment: JBoss AS 7.0.1
Reporter: Bill Meyer
Assignee: Jean-Francois Denise
Priority: Minor
In this example, no Data Sources already exist (clean config).
If I enter the following into the CLI and hit <tab>:
/subsystem=datasources/data-source=:<tab>
I get no operation hints. If I use a bogus resource name that doesn't exist and hit
<tab>:
[standalone@localhost:9999 /]
/subsystem=datasources/data-source=DoesNotExistDS:<tab>
add disable enable
flush-all-connection-in-pool
flush-idle-connection-in-pool read-attribute read-children-names
read-children-resources
read-children-types read-operation-description read-operation-names
read-resource
read-resource-description remove test-connection-in-pool
validate-address
write-attribute
I get all the operations available. This should be made more consistent. The
preference, IMO, would be to not have to specify a bogus name and still get the operations
list:
[standalone@localhost:9999 /] /subsystem=datasources/data-source=:<tab>
or simpler yet:
[standalone@localhost:9999 /] /subsystem=datasources/data-source:<tab>
(no empty equal sign).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)