This was probably pretty obvious to everyone but me, but removing the "ROOT.war"
folder from the jbossweb-tomcat50.sar folder under deploy did the trick - there were
probably conflicts because we deploy our application under the root context that this
WAR was apparently using
View the original
The same thing is happening in 3.2.5 as happened in 3.2.4
Charles.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840172#3840172
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840172
-
To add to the weirdness:
If I then hot redploy the EAR file after things fail the first time, the WAR
successfully deploys. If I shut down JBoss and restart it, the deployment fails
again, but succeeds after another hot redeploy. It seems like my WAR file is being
deployed before something el
Hi all,
I have an application EAR file which contains an EJB JAR file and a WAR file. Under
JBoss 3.2.2, everything works swimmingly. When trying to upgrade to JBoss 3.2.4
however, the EJB JAR file deploys fine but the WAR file will not deploy. I'm sure
there must be some configuration or li