In default/conf/jboss-service.xml towards the end you find DeploymentScanner settings. Change the URLs attribute:
<attribute name="URLs"> deploy/,file:/srv/images/ </attribute>
If there's a slash at the end, the directory is treated like deploy, and all subdirectories are deployed by default. But you can also specify adad.war at the end, without slash, and then only that one app. is deployed.
(I don't know if "file:" is always needed or not, I use it for individual wars and ears. In the above case it may be just the path.)
We still didn't solve the problem: context.xml ignored.
This one only add another local directory as deploy directory.
I still have the problem with "context docbase ignored". Anyone know how to solve this problem.
jeffgoa - PLEASE STOP POSTING your problem to every forum post that mentions external directories!!!
It seems that "modifying server.xml Context entry, adding docBase" works. The key on Windows is to add "c:\" before directory.
Does docBase work in context.xml that goes inside the ear? Not good to use the server.xml as that would be too invasive so is not preferred. We need to be able to hot-deploy these docBase changes - and not restart the whole server just for that.
This is absolutely ridiculous. Absurd. I have to edit a server XML file just to deploy an application that does not live in the JBOSS directory tree. Everytime a new JBoss comes out, I have to re-edit the same or a different XML file. BS. I need to be able to run "ant deploy" and have my CONTEXT.XML copied to the right place (hopefully JBOSS/deploy).
This is absolutely ridiculous. Absurd. I have to edit a server XML file just to deploy an application that does not live in the JBOSS directory tree.
Which xml file are you referring to? I'm confused because of your next statement:
I need to be able to run "ant deploy" and have my CONTEXT.XML copied to the right place