Hong Zhang wrote on 08/28/09 13:28:
>> As far as I can tell, the complete list of commands with comma separated
>> options is:
>>
>> create-connector-security-map
>> update-connector-security-map
>> update-connector-work-security-map
>
> There is also the deploy command. The --virtualservers option of the
> deploy command takes a comma separated list of the virtualservers. And
> the --libraries option of the deploy command takes a comma separated
> list of the libraries.
These aren't implemented using List<String>, they do their own tokenization.
I have no idea why. Any change to the framework's handling of lists won't
impact these. Probably they should be changed to allow the framework to
do the tokenization.
But this does point out that there are more commands that use comma as a
separator. If we were to standardize on one that would be supported by
the framework (option 3), comma may be more common.