Is there any particular reason for not sorting the subdeployments in those methods? Something really obvious I missed?
In my case I've got an ear file containing a sar (which sets up the data source for my beans) and the ejb-jar. Deploying the application is not a problem (sar gets deployed first and the beans find their DS). But undeploying doesn't work properly - the sar gets undeployed first and so the bean's tables (create-table and remove-table are true during development) don't get removed because the db connection is gone. So I changed the stop() and destroy() methods in MainDeployer slightly to sort the subdeployments (just like in init() etc. only added a Collections.reverse()). And ... it works perfectly. At least the way I expect it to work. So if anyone (Marc?) is interested I could submit this as a patch. (only if it makes sense - of course) Cheers, Torsten PS: I'm using 3.0.1RC1 ------------------------------------------------------- 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
