[jboss-jira] [JBoss JIRA] (WFCORE-421) cli tab-completion: filtering out operations not applicable to a resource
Jean-Francois Denise (JIRA)
issues at jboss.org
Wed Jan 11 09:05:01 EST 2017
[ https://issues.jboss.org/browse/WFCORE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Francois Denise reassigned WFCORE-421:
-------------------------------------------
Assignee: Jean-Francois Denise (was: Alexey Loubyansky)
> 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 at 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 at localhost:9999 /] /subsystem=datasources/data-source=:<tab>
> or simpler yet:
> [standalone at localhost:9999 /] /subsystem=datasources/data-source:<tab>
> (no empty equal sign).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list