Bill Shannon wrote:
> Two things I don't understand about the "view" approach...
>
> How does this solve the AMX problem? How does the AMX client,
> which uses JMX underneath, control which view it sees?
I don't think "views" of config beans solves the "AMX" problem.
I think we are tending toward making changes to AMX API in an
incompatible manner (by making methods accept/return strings alone).
>
> How do you handle the fact that the types of the attributes are
> different in the different views? E.g., boolean vs. String.
>
A view (I guess) returns a proxy that views the config bean world in
a (possibly) type-safe manner. To that effect, there is a raw view which
is type-unsafe and there is a translated view that is type-safe.
Again, this applies to lower level config and not directly related to
publicly exposed AMX API.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>