I think Manish meant that the sever must be running for the commands to
be executed.
yes there is a good reason for this change, most commands are
implemented on the server side as glassfish dynamic nature allows for
very different installations to have very different capabilities
(different set of commands), yet you would want to keep the same asadmin
client to talk to all of them.
Jerome
Kedar Mhaswade wrote:
> That's not right. Although most of the internals have changed, nothing
> has
> changed as far as asadmin "interface" is concerned. add-resources
> could be run
> in V2 only with running domain. So is the case with v3 Prelude.
>
> asadmin and all its commands are "public interface" of GlassFish. We
> could not
> change it in an incompatible manner even if we had other (strong)
> reasons to
> do so.
>
> If you think there is indeed an incompatibility, please let us know
> because
> v3 Prelude is not 100% compatible with V2 and we know it.
>
> -Kedar
>
> Manish Gupta wrote:
>> It seems that Glassfish should be running to execute most of the
>> asadmin commands like add-resources in v3...it is not a case with v2.
>> Any reason for this change in v3??
>>
>> Manish.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>