-
1. Re: JBoss doesn't autodeploy
darranl May 11, 2005 7:41 AM (in response to bertsura)If you started JBoss using the run script with no arguments this means that you will be using the default configuration.
In this case you need to put the war in {jboss.home}/server/default/deploy
If you passed the arguments '-c all' to the run script this means that you have started the all configuration.
In this case you need to put the war in {jboss.home}/server/all/deploy
If you passed the arguments '-c minimal' to the run script this means that you have started the wrong configuration, you should use one of the two configurations above.
Once you have the correct deploy folder something should be displayed on the console. -
2. Re: JBoss doesn't autodeploy
bertsura May 11, 2005 10:12 PM (in response to bertsura)I used '-c all' and put the war in the correct folder but it doesn't autodeploy. Do I have to edit the war? As I've said, it deploys on Tomcat, so I don't understand why it doesn't deploy on JBoss.
-
3. Re: JBoss doesn't autodeploy
bertsura May 12, 2005 3:40 AM (in response to bertsura)I found out why it doesn't autodeploy. It seems I did have to edit the war by adding a jboss-web.xml. It's deploying already, but now I'm getting a "No suitable driver" error. I've already added the driver in -ds.xml and the jar that contains it in server\all\lib.