Patches item #579731, was opened at 2002-07-10 19:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=579731&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Torsten Schlumm (schlumm) Assigned to: Nobody/Anonymous (nobody) Summary: MainDeployer's stop and destroy methods Initial Comment: The init(), create() and start() methods in MainDeployer sort the list of subdeployments before iterating over it. In contrast to this the stop() and destroy() methods don't sort this list and therefore the undeployment order could be wrong. Example: - put a sar (which configures the data source your EJB's use) and the ejb-jar into an ear (beans have remove-table set to true) - deploy the ear (order is right: 1. sar 2. ejb-jar) - undeploy the application (order is wrong: 1. sar 2. ejb-jar) - when the server tries to remove the db tables the data source is already gone. Solution: Sort the list of subdeployments in stop() and destroy() like in init() etc. - just in the reverse order. Cheers, Torsten ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=579731&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
