Yes, I think blocks should be able to be managed individually.
I think making management at the service level is a good start, but you really want to manage blocks, IMHO. Maybe if the management of a block was an aggregate of all the services it implements + any block specific items?
I don't think that the services a block provides should be aggregated w.r.t to management. This of course
is problematic if there are intra-block dependencies for the provided services!
What would be nice, would be a way to deploy an app in an "unconfigured" state, and then let the user come and use a JMX tool to configure it.If your MBean itself persists changes made from operations to a config file, then you can use any
JMX Agent which allows the running of operations (such as the HtmlAdaptor agent). That's a big IF.
Otherwise, you need to have a separate tool/agent which can mangle an MBean's config file. There is
no generic tool for doing this. I suspect this is because everyone does configs in their own way ;)
cheers Pratik
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
