Test
-----Forwarded Message-----
From: Adrian Brock <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Service Lifecyle confusions - potential fix
Date: 07 Mar 2004 01:23:35 +0000
Hi Scott,
Are you working on the Service lifecycle?
I saw you replaced common's state machine implementation.
I was thinking that there should be an extra indirection
to avoid the confusion caused by people clicking stop() and other
operations in the console where dependencies are not taken into account.
My idea is that you implement an extra operation in ServiceMBeanSupport
public void jbossServiceLifecylce(String operation) throws Exception
{
if (operation.equals("create"))
{
// the current create() method
}
etc.
}
This would be invoked from ServiceController.ServiceProxy when
it is implemented by the MBean.
This would allow us to change the current
ServiceMBeanSupport.create() to be:
serviceController.create(serviceName);
etc.
Now clicking stop() in the console goes via the service controller
making sure dependencies are also stopped.
This doesn't fix the problem for MBeans that do not extend
ServiceMBeanSupport. These would still do the old behaviour.
Similar changes would be required to ServiceDynamicMBeanSupport
and the XMBean descriptor include.
Regards,
Adrian
--
xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Director of Support
Back Office
JBoss Inc.
xxxxxxxxxxxxxxxxxxxxxxxx
--
xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Director of Support
Back Office
JBoss Inc.
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
