[jboss-jira] [JBoss JIRA] Commented: (AS7-1878) CLI commands inconsistent for executing operations

[Alexey Loubyansky (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629560#comment-12629560 ] 

Alexey Loubyansky commented on AS7-1878:
----------------------------------------

> The preference, IMO, would be to not have to specify a bogus name and still get the operations list:

This would be wrong because this would be a wrong operation request format.
On the other hand, specifying a non-existing name in some cases will be a legal use-case, e.g. if you want to execute operation 'add', in fact, in this case, specifying an existing datasource name will be wrong.

So, to be really correct here, if the name doesn't exist the tab-completion should suggest only the operations that can be performed on non-existing nodes (same for the existing ones). I would agree to do it as long as this kind of info was available in the model description. Otherwise, in general, I don't know which operations are applicable for which nodes.

> CLI commands inconsistent for executing operations
> --------------------------------------------------
>
>                 Key: AS7-1878
>                 URL: https://issues.jboss.org/browse/AS7-1878
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: CLI
>         Environment: JBoss AS 7.0.1
>            Reporter: Bill Meyer
>            Assignee: Alexey Loubyansky
>            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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira