I just worked through an issue where my development JBoss server started
directing EJB calls to my local JBoss server.
It turns out I accidentally copied jndi.properties from our client app into a
JAR on my local JBoss server. The new jndi.properties pointed at the
development JBoss server and
Touch the EARs META-INF/application.xml file and it'll reload everything in the EAR
including your web app.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843437#3843437
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=38
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
