Hi Ant, Obviously the easiest way to do this is adding whatever methods we need into classes where those methods reside naturally. But I do not see those methods can be qualified as management APIs. If your intention is to have APIs that potentially can be exposed to management/instrumentation (e.g., to JMX MBeans or SNMP), I think there is a neater way to do this. Instead of having Tuscany core "polluted" by management stuff, we can have a plugable Tuscany management implementation. For example, each component that needs instrumentation will have a corresponding instrumentation component, management APIs are defined in instrumentation components, the call to management APIs can be delegated to the real runtime APIs or can be implemented using management specific logic (such as service counter). Management APIs in instrumentation component can be marked by management annotations, such way allows the dynamic generation of JMX Mbeans. I am not sure whether or not we have a general Tuscany management/instrumentation story on the roadmap, just something to think about. If you have interest, you can also take a look at Celtix management.
Cheers, Jervis Liu -----Original Message----- From: ant elder [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 31, 2006 11:44 PM To: [email protected] Subject: SCA Management API for Tuscany How about having a management API for Tuscany? The use case i have right now for this is so a J2SE client to can find out what are the valid service names it can use in the locateService method on the org.osoa.sca.ModuleContext interface. This is to make the JavaScript interactive client able to automatically register all the available services to the JavaScript environment, see: http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200605.mbox/[EMAIL PROTECTED] So that could be a method like: public List<String> getServiceNames(); Any suggestions as to where a method like this could go and how to get at one of those things? ...ant See the thread: http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200605.mbox/[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
