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.
I am just starting to package my web application project as a WAR file and am running into differences between the configuration for Tomcat vs Jetty vs JBoss vs Websphere, etc.
Should I try to configure some super-smart an all-in-one WAR file, or should I create different Maven profiles to create different WARs for each app server?
I don’t think I should create a separate Maven module for each app server WAR, should I?
I try never to ship configuration inside a war. The code shouldn’t care what environment it’s shipped into. It makes deployment more complex, but the flip side is that you can easily push out a config change and have to be concerned about accidentally deploying code changes to an environment.
This advice applies doubly in this case as it seems like you have the challenge of different environments and different containers.