As a followup to this, and to fix some other bugs, I rewrote the code
that handles parameter processing for quotes and escapes. I think the
new code is still compatible, but if you notice any changes in this
area, let me know.
Bill Shannon wrote on 08/28/09 18:09:
> I just checked in a change (which was discussed on admin_at_glassfish)
> to the implementation of the server side admin command option
> processing.
>
> Many admin commands take options that are a list of values, the most
> common example being a --property option that takes a list of properties
> separated by colons.
>
> In v2, some of these options used comma as a separator. In v3, they
> were using colon everywhere. My change fixes this to be compatible with
> v2. You might notice this change in commands such as
> create-connector-security-map and update-connector-security-map.
>
> If you notice any other unexpected changes in the way lists of values
> are handled for admin command options, let me know.
>
> If you know of any other places where lists of values aren't handled
> compatibly with v2, let me know.
>
> Thanks.