dev@glassfish.java.net

Re: CLI Framework for JMX

From: Jane Young <Jane.Young_at_Sun.COM>
Date: Sun, 29 Oct 2006 07:50:15 -0800

CLI Framework (admin-cli/framework) is compliant with Sun's CLIP
(Command Line Interface Paradigm) which is in the works of getting Open
Source'd.


kedar wrote:

> Good question.
> One thing we should all know is the admin-cli/cli-api submodule is a
> generic
> JMX client that works independent of any implementation that uses it.
> For example, it is possible that you can direct the cli-api to any
> JMX compliant server and it will do its job perfectly all right.
>
> BTW, cli-api is not actively maintained. Talk to Lloyd Chambers
> (llc_at_dev.java.net)
> for details.
>
> admin-cli/commands is specifically geared towards GlassFish
> administration commands.
> The use of XML for declaring the command names obviously advantageous
> because it
> improves development time.
>
> There are some inherent differences in the above two ways and they
> have evolved
> differently over time. admin-cli/framework is used by commands module
> and provides
> some general purpose command parsing, environment variable support
> etc. in accordance
> with the schema of the XML that you refer to. In short, it can very
> well be
> used by any Java program to impart a *powerful* command line parsing
> support.
> Talk to Jane Young (janey_at_dev.java.net) about it.
>
> Kedar
>
>
> Jim Jiang wrote:
>
>> For admin-cli project, there are 3 packages: framework, commands,
>> cli-api.
>> In CLI-framework, an xml file was used for defining the commands.
>> / <Command name="list-domains"
>> classname="com.sun.enterprise.cli.commands.ListDomainsCommand"
>> numberofoperands="0" usage-text="list-domains [--terse=false]
>> [--echo=false] [--domaindir domain_directory]">
>> <ValidOption name="terse"/>
>> <ValidOption name="echo"/>
>> <ValidOption name="domaindir"/>
>> </Command>
>>
>> /But for JMX command, the command was defined as java method:
>> for example, com.sun.cli.jmx.cmd.DeleteCmd:
>> / getNumRequiredOperands() {
>> return( 1 );
>> }/
>> ...
>>
>> Could anyone give any explanation for why no different way used for
>> the command definition?
>>
>> Thanks,
>> Jim
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>