Also, with it as an admin command you don't have to worry about writing
shell and batch scripts, you don't have to worry about a help framework.
The usage message is created for you. It would fit naturally into the
documentation. You just would need one VerifyMulticastCommand.java file.
Tom
On 7/28/2010 2:21 PM, Byron Nevins wrote:
> You wouldn't need to make admin code dependent on GMS code. It's the
> other way around.
> take a look at [cluster/cli] to see how external modules can use the
> CLI framework.
>
>
> On 7/28/2010 1:07 PM, Bobby Bissett wrote:
>> On Jul 28, 2010, at 11:34 AM, Tom Mueller wrote:
>>> Just curious. Would this make sense as an asadmin local subcommand
>>> rather than introducing a new script? We already have a
>>> "verify-domain-xml" command. We could have "verify-multicast".
>>
>> It's ok with me conceptually, but in terms of time constraints it
>> could be an issue. It would mean that the admin code has a dependency
>> on the gms impl code though.
>>
>> Anyone else have an opinion?
>>
>> Cheers,
>> Bobby
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>