have you tried to deploy your ear exploded. Then you could keep your file(s) in your folder structure and JBoss will redeploy your application every time you change the files.
Thanks Anders, for replying.
Actually my application structure is as follows:
| |____ conf files.xml
As shown above, myApp.ear is exploded. This contains myApp.jar which is NOT exploded. myApp.jar inturn contains the configuration files. Right now during development, we plan to keep the ear exploded. But once the product is rolled out, we MAY NOT be having the ear in exploded form. So placing the conf files in the ear might not be useful
I tested my suggested solution, and it didn't work. It seems like JBoss will only redeploy the exploded application if you edit the deployment descriptor.
In my case I've a web application that I deploy exploded:
webapp.war (exploded) |---WEB-INF |---web.xml (changed this one, JBoss redeployed app) |---jboss-web.xml (changed this one, JBoss didn't redeploy app) |---my-conf.xml (changed this one, JBoss didn't redeploy app)
It seems like JBoss will only redeploy the exploded application if you edit the deployment descriptor.
Ya you are right. Exploding the ear wont yield the results.
Thanks for spending your time on this :-)