This is my bug, I had made the command fail if obsolete options are
used. Will fix this.
Tom Mueller wrote:
> Here's a test case:
>
> $ asadmin create-cluster --haagentport 5 ctest
> CLI031 Warning: Option "haagentport" is obsolete and will be ignored.
> remote failure: Exception while adding the new configuration
> org.jvnet.hk2.config.TransactionFailure: Obsolete options used. :
> org.jvnet.hk2.config.TransactionFailure: Obsolete options used.
>
> Command create-cluster failed.
>
> So it looks like the command framework is doing the right thing, but
> the config framework is not.
>
> Tom
>
>
> On 8/11/2010 11:24 PM, Bill Shannon wrote:
>> Whether or not you specify an obsolete option shouldn't change
>> the exit code. If that's not what you're seeing, show me a test
>> case.
>>
>>
>> Tom Mueller wrote on 07/21/2010 08:27 AM:
>>> The comments in Param.java say the following about the obsolete value:
>>>
>>> /**
>>> * Returns true if this parameter is obsolete.
>>> * Obsolete parameters produce warnings when used in asadmin,
>>> * are ignored, and are not included in the command usage.
>>> *
>>> * @return true if the parameter is obsolete
>>> */
>>> public boolean obsolete() default false;
>>>
>>> The "are ignored" part apparently doesn't extend to the exit code of
>>> the command.
>>>
>>> Tom
>>>
>>>
>>> On 7/20/2010 10:18 PM, Jennifer Chou wrote:
>>>> Hi Bill,
>>>>
>>>> We wanted to verify how the commands should handle the HADB
>>>> attributes.
>>>> Right now the code marks them as Obsolete. It does not show-up in
>>>> the usage text. And if it's specified the command fails.
>>>> However, the design spec had mentioned that the option is to be
>>>> ignored, with a warning that the option has been deprecated and may
>>>> not be supported in a future release.
>>>>
>>>> create-cluster in v2.1.1 had
>>>>
>>>> [--hosts hadb-host-list] [--haagentport port_number]
>>>> [--haadminpassword password] [--haadminpasswordfile file_name]
>>>> [--devicesize devicesize ] [--haproperty (name=value)[:name=value]*]
>>>> [--autohadb=false]
>>>>
>>>>
>>>> delete-cluster and start-cluster had
>>>>
>>>> [ --autohadboverride={true|false} ]
>>>>
>>>>
>>>> And I believe we are thinking to not support setenv anymore on
>>>> start-instance
>>>>
>>>> [--setenv (name=value)[:name=name]*]
>>>>
>>>>
>>>> Ref:
>>>> http://wikis.sun.com/display/GlassFish/V3.1Clustering#V3.1Clustering-ClusterAdminCommands
>>>>
>>>>
>>>> Thanks,
>>>> Jennifer
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>