In the case of Tomcat, you can also store these in a Context.xml file,
which can be configured differently for each server (including your
development machine). The context.xml file can be unique to each
Tomcat instance, and live in Tomcat/conf/context.xml or
Tomcat/conf/Catalina/localhost/context
Whether you use AppModule.java, app.properties, or web.xml, it's still
hard-coding. Only constants belong in there.
Environment-specific properties can be set as system properties before
starting the server,
eg. for JBoss on Unix: setenv JAVA_OPTS '-Dtapestry.production-
mode=false -Dtapestr
How are about other values like production_mode, cookie age which have
different values in DEV, QA and Production environments?
Even put it in the web.xml is not good either? I cannot change web.xml when
we release software to QA and production.
Thanks
-B
Harald Geritzer-2 wrote:
>
>
> you c
you can put them into your web.xml file:
http://java.sun.com/dtd/web-app_2_3.dtd";>
MyApp
tapestry.supported-locales
de
..
bongosdude schrieb:
hardcoded value in AppModule.contributeApplicationDefaults method is not a
best practice.
class AppModule {
..
