dev@glassfish.java.net

Re: implementing a cli command

From: Jerome Dochez <jerome.dochez_at_oracle.com>
Date: Fri, 30 Jul 2010 12:37:37 -0700

On 7/30/10 9:42 AM, Marina Vatkina wrote:
> Jerome,
>
> transaction and ejb (and I think connector) commands live under their
> respective modules. Should we be consistent?
you mean transaction and ejb related cli commands ? I am not what
inconsistency you are trying to point out...

jerome

>
> thanks,
> -marina
>
> Jerome Dochez wrote:
>> Since it will depends on Gms I would put it in cluster/gms. It does
>> ont make sense to run this command if gms is ont present, right ?
>>
>> Le 30 juil. 2010 à 17:15, Bobby Bissett <bobby.bissett_at_oracle.com> a
>> écrit :
>>
>>>> [...] don't see offhand why I should implement AdminCommand vs
>>>> extending CLICommand.
>>> And I've already reversed my thinking on this.....
>>>
>>> Are there any guidelines for these things (besides inferring intent
>>> from other examples)? E.g., should this command be in cluster/cli or
>>> cluster/admin or should I just put it in the cluster/gms-adapter
>>> module where the real work is going to happen anyway?
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>