Dan Adams wrote:
I was wondering what people ways people have found with tapestry to make
launching a .war easier? For instance in my app I test locally using
jetty but then have a server that releases get put on at the end of
every iteration. Here is an example of what would need to change:
- email address of support staff. right now they go to me and are stored
in the main property file but it would nice to have another property
file of the real values that gets swapped in
- the database connection info
- enabling/disabling certain features in the system based on whether it
is development or production
I'm just curious about some of the ways that people have done this.
Thanks. :)
Check out the servlet specification and look for env-entry (for example
chapter 13 of servlet 2.4). Most J2EE servlet containers lets you
override the values provided in web.xml in the war-file. How this is
done is different between the containers (tomcat can have configuration
in the conf/Catalina/localhost directory, weblogic have weblogic.xml et c.).
Why implement your own configuration framework when the servlet
specification already provides it :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
