The local module should never be loaded by the DAS. The remote module
should never be loaded by asadmin.
I like your suggestion regarding Java package names.
Tom
On 9/1/2010 12:47 AM, Rajiv Mordani wrote:
> Can we not use package names like
>
> com.sun.enterprise.admin.cluster.cli.local and
> com.sun.enterprise.admin.cluster.cli.remote and
> com.sun.enterprise.admin.cluster.cli.hybrid, for example, and put
> them all in the cli module? Why are they split across two modules?
>
> - Rajiv
>
> On 8/31/10 10:36 PM, Vijay Ramachandran wrote:
>> On 8/31/10 10:33 PM, Rajiv Mordani wrote:
>>> Currently I see that the cluster related commands are in two modules
>>> and packages - some of them (StartCluster, StartInstance etc) are in
>>> the cluster-admin module in com.sun.enterprise.v3.admin.cluster
>>
>> The above are remote commands
>>
>>> and some of them (SynchronizeInstance, SetupSshKey,
>>> DeleteInstanceFileSystem etc) are in the cluster-cli module in
>>> com.sun.enterprise.admin.cluster.cli package.
>>
>> The above are local commands. That is the distinction that has been
>> followed.
>>
>> Vijay
>>
>>> Any guidelines of which to use when? Also why are they spread across
>>> these two packages / modules?
>>>
>>> - Rajiv
>>>
>>> ---------------------------------------------------------------------
>>> 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
>