Hi Meeraj, Nice summation - thanks!
>There are two aspects we are discussing here, >1. How the management mechanism is implemented >2. How the management interface is extracted from managed components >On the first aspect this is how I see it, > ... >5. TuscanyServer will use JMX for management I'd really like to make this configurable. I agree that for the java implementation, JMX will be the easiest to do initially, but that won't help the C++ implementation. If we use some of the same machinery for supporting multiple management mechanisms that the runtimes will use, then we can leave a path for C++ and Java implementations to participate in the same "management fabric". We need to think about how to support events raised by managed resources and relationships between managed resources. The focus in JMX seems to be on properties and operations (although JMX does support an event model and a relationship service), but for WSDM, WS-Notification is a big part of the spec, and the ability to script automatic management behavior using something like BPEL is an important aspect of the vision. What are your thoughts on multiple concurrent management mechanisms? I can imagine a case where operations may want jmx and web-services based management access to the same SCA instance, which means events and relationships would need to propagate between the two implementations. Can we auto-wire multiple management service implementations? >On extracting the management information .. >2. The JMX annotations we discussed earlier may not be a possibility >depending on whether they will get adopted as part of the osoa annotations >or not. We don't want the application services littered with Tuscany >annotations. What are the odds of getting this done? Do we know if manageability is on the spec group's to-do list? 4. We can always go back to some sort of management binding in the scdl. We may have to do this anyway for containers that we can't introspect (as pointed out earlier in this thread). I'm off to synch my Tuscany tree so I can understand the rest of your discussion. ;-) Cheers, Joel The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
