Make a new directory under your deploy directory named "deploy.last" and put the VolatilityManager EAR in there.
Or, I think as of 3.2.3 you can specify a tag in your application.xml that will let JBoss know to deploy one before the other and redeploy both if the one changes. I ran into a bug with this though that prevented hot redeploy from working. Its supposed to be fixed in 3.2.4 that's rumored to be out soon. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825022#3825022";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825022>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
