From: fabcipriano <nu...@jb...> - 2005-07-30 02:10:41
|
I agree with distribute, undeploy and redeploy procedure, but in my insigni= ficant opinion I think that start and stop should use MainDeployer. Because JBoss code map the JSR-77 status (starting, running, stopping etc) = to the ServiceMBean(starting, started, stopping etc). This form the JSR-88 = implementation will be like a suggestion of the j2ee deployment 1.1 specifi= cation item 4.6.2 Besides implementation of getAvailableModules and getNonRunningModules with= jsr-88=20 implemented this way it will force us to read all modules in the local disk= to find out the nonRunning modules.=20 In the other way the JSR-88 implementation let open this question when says= in the item 4.3: "A vendor may choose to initialize an application?s running environment when the archive is distributed to the system or wait until the= start action is called. The only requirement is that the application is no= t available to clients until the start action is called. Similarly a vendor= may choose to shut down a running application?s environment when stop is c= alled or wait until undeploy is called. The only requirement is that the ap= plication is made unavailable to clients when the stop action is called." I=C2=B4m using MC4J with jboss jsr-88 with the JBAS-2002 modification and I= had no problem until now. I can stop, start a Module and see the state in = the screen only a undeploy make my modules dissapear from the GUI. Am I missing something ? View the original post : http://www.jboss.org/index.html?module=3Dbb&op=3Dv= iewtopic&p=3D3887408#3887408 Reply to the post : http://www.jboss.org/index.html?module=3Dbb&op=3Dpostin= g&mode=3Dreply&p=3D3887408 |