In V2, even though elements like <resources> existed, they were
omitted as MBeans; there was no AMX "ResourcesConfig" MBean.
In implementing V3, I want to keep things generic--no special code,
especially important in a modular system.
Accordingly, I would like to move all resource related methods (create/
remove/get) into a ResourcesConfig MBean.
For clients, the change would look like this:
domainConfig.getResources().create/remove/
get<ResourceName>Config(...) proposed V3 approach
vs:
domainConfig.create/remove/get<ResourceName>Config(...) proposed V3
approach
Similar issues exist for other elements such as <node-agents>,
<configs>, <load-balancers>, etc.
Lloyd
---
Lloyd L Chambers
lloyd.chambers_at_sun.com
Sun Microsystems, Inc