Hi Jeremy, This is interesting stuff...
>The other thought was about how a component could expose a management >interface. One option would be to support <binding.jmx> for >attachment to a service; however, this would require a componentType >sidefile. Another would be to support an @Management annotation on a >service interface. With both of these the selected service would be >registered as a Dynamic MBean. A fallback option would also be to >recognize the component as a Standard MBean (i.e. it would have a >*MBean interface). I like the notion of a technology-agnostic @Management interface, as it could support a management binding to JMX or WSDM (or SNMP, for that matter). The management technology layer could then be decoupled from the component definitions, allowing the management layer(s) to be mixed in as an SCA service. Of course, for non-java components, you're stuck with a side-file of some sort. 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]
