Class loading cannot be the issue because all jars in the deployment are added the the classpath of the deployment before any component is started. People to have dependencies between components that can require a specific startup ordering. We have not in the past used the application.xml declaration order as any indication of the startup order. You would have had to of used jmx level dependencies. As of 4.0.0RC2 and 3.2.6RC2 the we maintain the application module order as that the order declared in application.xml so that the start order of EAR components is deterministic and equal to that of the declaration order.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847742#3847742 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847742 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
