Scott Stark wrote:
- This is beyond the current doman model discussion. This is truly MDR level overrides of either domain.xml of ManagedComponent properties at a level above the server
While we are looking at doing just the server side up front I think it's an important question to answer. It's really a question of what the jboss-management ManagedComponent view represents. Is it a representation of the client view, and thus has a direct mapping to a future multi-server domain.xml, or is it a normalized/realized post-evaluated view? Long term, It can't really be used as a client api if it is solely the latter.
It seems like it could be both though, and that's compatible with the approach you describe. A client can edit a view (one that could just be a bunch of managed components, or it could even be static metadata since the model is itself static), and that view would then be transformed into something a service or deployer could act on. In the end this would be realized in changes to the runtime MOs.