On 11/03/2011 5:03 PM, Greg Akins wrote:
Thanks for your reply.
On Fri, Mar 11, 2011 at 3:14 PM, Ron Wheeler
<[email protected]
<mailto:[email protected]>> wrote:
On Tue, Mar 1, 2011 at 9:27 AM, Greg Akins<[email protected]
<mailto:[email protected]>> wrote:
You would be surprised at the amount of discussion there is on
this point.
You have it right.
I can imagine :-)
Keeping your server(localhost, all the test, all the productions)
configurations out of your war files is the right way to go for
exactly the reason that you identified.
Getting everyone to use the same localhost configuration is
probably the hardest part but really makes the team function more
effectively once you have it in place.
You're saying to keep everything out of the configs? Even localhost
configuration?
One of the things I love about Maven is that I can checkout project
and run mvn test without having to copy other configuration files, or
do any other setup.
I wouldn't be able to do that without SOME configuration files. Am I
missing something?
No. You are exactly right.
However, the new programmer would only have to do this once.
This is a much better situation than the errors that happen if localhost
or test configurations get into production.
Ron
JNDI is a good way to manage server confiurations.
Separating Deployment from Development with JNDI
We are dealing with a legacy "home-built" server. It would be a bit
much to add JNDI at this point. Our newer code already takes
advantage of JNDI. But we still need configs for log4j.properties and
some key certificates that have to be managed.
--
Greg Akins
http://twitter.com/akinsgre
