• Post Reply Bookmark Topic Watch Topic
  • New Topic

Environment specific properties and WAR file deployment

 
Ted Bell
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
I was wondering what the consensus was here about including environment-specific configuration information in the WAR file (like database connection info, etc) as environment entries, as in the web.xml. We have for some time here followed another practice. Any environment specific properties are placed in a properties file and deployed to a shared/classes folder and referenced on the classpath.
This allows us to move the WAR file from dev to test to production without requiring any modifications. I was having second thoughts about this approach, since it is really does not follow the application assembler/deployer role based model.
Thought I would get some feedback from other ranchers on your common practices.
Thanks.
 
Eric Sexton
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Are you Art Vandelay the architect or the judge?
 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Oh if you put your properties file in a shared folder, is it not accessible to the client? The reason why we used web.xml for the environment-specific information is that everything under WEB-INF is not accessible by the client... I don't know if you have any other ways to that shared folder that contains properties file to keep away from the clients' access... Can u share your experience here? Thank you...
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!