Hi, Cheng
> I noticed some commands take target operand, and others take target
> options. What's the rules for providing target value?
>
> For ex:
>
> asadmin list-components --target cluster1 (Failed as option)
> Invalid option: --target
>
> asadmin list-components cluster1 (Passed as operand)
> Command list-components executed successfully on server instance
> instance1
> Command list-components executed successfully on server instance
> instance2
Yes, I have implemented the list-components command to be v2 backward
compatible (though like Bill I am not sure why it was operand instead of
an option).
> (The doc says for list-components, the target operand is deprecated
> and ignored. But it turns out it's still significant)
Where do you see this? We should change this to say the same thing as v2
doc as we are implementing the same way.
Thanks,
- Hong
>
>
> asadmin list-jndi-resources --target cluster1 (Passed as option)
> Command list-jndi-resources executed successfully on server instance
> instance1
> Command list-jndi-resources executed successfully on server instance
> instance2
>
> asadmin list-jndi-resources cluster1 (Failed as operand)
> Command list-jndi-resources does not accept any operands
>
> Thanks,
> -cheng
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>