Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
A very simple question. I have a .war(~40MB) file to be run on JBoss.
What is the best practice for deployment: Should the war file be deployed in exploded format? Or not?
I ask because if its exploded then I’ve a choice of updating my properties file anytime I choose to (and need not make a new war every time I change the properties file).
But I’m not sure if deploying a war in exploded format is the best practice.
Please help me realize. 🙂
Modifying the exploded contents is certainly faster and more efficient, but one consideration is auditing and traceability. One advantage of only deploying WAR files and treating them as “sealed” is that any changes you make will have to be captured in your source code management system. You certainly don’t want people to have the ability to change whatever they wish in your application’s configuration without some kind of audit trail.
The Java EE separation of concerns usually means that the developer of the WAR is not the same person as the admin for the app server. If the developer does not have direct access, that means that folks who don’t know the application thoroughly are making changes.
I’m not defending the extreme mentality that forbids developers from modifying an exploded WAR, just pointing out an alternative view for your consideration.