Wrong start and create notification order in EARDeployer -------------------------------------------------------- Key: JBAS-4221 URL: http://jira.jboss.com/jira/browse/JBAS-4221 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.5.GA Environment: Java version: 1.5.0_10,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Server VM 1.5.0_10-b03,Sun Microsystems Inc. OS-System: Windows 2000 5.0,x86 Reporter: pgervais Assigned To: Dimitris Andreadis In the org.jboss.deployment.SubDeployer file the documentation on the different notification types says that all the notifications are emitted when the event has been completed, e.g: when a sub deployment has been started (not starting) In the org.jboss.deployment.EARDeployer file, the call to super.start and super.create is called at the beginning of the start and create method, the call to super should be done at the end, when the deployement has been created and when it has been started. The code is ok for the init, stop and destroy methods. I also verified the calling order in the EJBDeployer, EJB3Deployer and AbstractWebContainer and they are as specified in the SubDeployer. -- 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