If you change the URLs attribute so that it no longer contains the deploy directory, then yes, none of the services currently located in that directory will get deployed. Considering that these services include the web application deployer and the servlet container, not deploying them will prevent web apps from working also.
You have several options:
A) Succumb to conventions and deploy your web app to the deploy directory.
B) Rather than replacing the URLs attribute value, add a second entry to it, using a comma to separate the entries:
<attribute name="URLs"> deploy/, /full/path/to/your/app.war </attribute>
Note that you can add as many paths as you like, all comma-separated. Note, however, that only the first path is hot-deployed (if you do not understand what this means, you should use option A until you do understand it).
Thanks for your reply!.. i understand both options, and already experimented both already.. but honestly, I don't like neither of them. I'm seeking to see if it's possible to relocate the web application deployer and EJB container to my own exploded directory, instead of depending on the /deploy directory.
Please let me know.
Thanks a lot
but honestly, I don't like neither of them.
Any specific reason? Maybe we can't point you to something else if we know why exactly this option isn't feasible :-)
I guess I personally feel deploy directory deploys more services than I really need.
like.. do i really need jboss-aop, jmx-console and so on? I think I really just need ejb3.deployer and jboss-web.deployer and jmx if i want to usea JEE server right?