[
http://jira.jboss.com/jira/browse/EJBTHREE-711?page=comments#action_12343729 ]
Carlo de Wolf commented on EJBTHREE-711:
----------------------------------------
The container is stopped at Ejb3Deployment.java:501 and Ejb3Deployment:504.
It appears that container.stop() is redundant.
Note that Ejb3Deployer.startService & Ejb3Deployer.stopService are very asymetrical.
Is this by design?
During undeployment stop is being called twice
-----------------------------------------------
Key: EJBTHREE-711
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-711
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Carlo de Wolf
Fix For: EJB 3.0 RC10 - FD
After destroy is called on the container, stop is called again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira