Lloyd L Chambers wrote:
> This will be done today.
>
> AMX is confronted with the following issue:
>
> - In V2, certain attributes were exposed as String[], but stored as
> String in domain.xml. This was handled somewhat generically, but the
> delimiter might have varied between attributes (not sure). In any case,
> each AMX interface had an 'Impl' class, so these cases could be handled
> specially if need be.
>
> - there is no a-prior way to know the delimiter and/or escape sequence
> to stringify/destringify String[] <=> String; in general AMX cannot
> know the "right" thing to do. In a modular system with arbitrary config,
> this is a problem.
>
> PROPOSAL (incompatible with V2)
>
> Change the (few) String[] attributes to String
> (this doesn't include artificial attributes that have to remain as [],
> such as getJVMOptions()).
>
> Examples include com.sun.appserv.management.Libraries:
> String[] getLibraries();
> void setLibraries(String[] libs);
Since you can find the few attributes that need to be changed, you can
figure out what delimiters they were using.
If they're all using the same delimiter, why not just build that in as part
of the specification and leave the API alone? Or is the problem that you
can't know which fields to apply this to in an extensible system?