|Were talking about the org.jboss.util.Service interface still. All
|the SC does
|now is maintain an ordered list of Service instances and it invokes the
|init/start/stop/destory methods in the registration order on these
|as before.
|Now it is invoking through a Service interface rather than the MBeanServer.
Right, you check the interface first for the actual calls... hardcoded
init/start/stop/destroy... ok
|By default it is still simple and lightweight. There has been a
|proxy introduced
yes
|but this simply ensures that if an mbean only had a couple of the Service
|methods in its mbean interface we are no longer invoking the unimplemented
|methods. So for example, the com.sun.jdmk.comm.HtmlAdaptorServer mbean
|only implements start()/stop() and now these are the only methods
|the dynamic
|proxy attempts to invoke on the mbean. Previously init() and destroy() were
|invoked as well as the resulting exception silently ignored.
Strickly speaking start and stop and the only ones that 77 will require.
marc
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
