Hi Jim, Most Celtix management codes are located under trunk\celtix-rt\src\main\java\org\objectweb\celtix\bus\management, an example of how instrumentation component is written can be found in trunk\celtix-rt\src\main\java\org\objectweb\celtix\bus\busimpl\CeltixBusInstrumentation.java.
Celtix management design note can be found from https://wiki.objectweb.org/celtix/Wiki.jsp?page=ManamgentDevPlan, and Celtix management manual is available from trunk\celtix-distribution\src\site\docs\UserGuides\management.pdf Let me know if we are considering adding management capabilities into Tuscany. I would be very interested to do some work in this area. Cheers, Jervis Liu -----Original Message----- From: Jim Marino [mailto:[EMAIL PROTECTED] Sent: Friday, June 02, 2006 1:21 AM To: [email protected] Subject: Re: SCA Management API for Tuscany Hi Jervis, This is an interesting approach. Could you point the list to a Celtix (Java) package where we could start to look and base a discussion around? Jim On May 31, 2006, at 8:08 PM, Liu, Jervis wrote: > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
