This week's giveaway is in the EJB and other Java EE Technologies forum.
We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes Best practices for configuration for staging environments Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Best practices for configuration for staging environments" Watch "Best practices for configuration for staging environments" New topic
Author

Best practices for configuration for staging environments

Allexicus Kernikus
Ranch Hand

Joined: Oct 07, 2009
Posts: 42
In a department meeting we had a discussion on changing our methods on addressing staging environments.

Up to now we generated a deployable for each staging environment (e.g. DEV, QA, PROD). From now on we want to generate one deployable and load the configuration file at runtime.

Is that the right way to go? Does it really bring along additional flexibility?

Also, a good how to/best practices guide would be very much appreciated.

Thanks in advance! - LX
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Best practices for configuration for staging environments
 
Similar Threads
Best Practices/Recommendations
cvs best practices?
Java Developer, Cincinnati, OH 11/11/07
logging version number at runtime
Loading Configuration files