I think Josh is on the right track ... that's essentially why execution-mode was introduced. Often,. the execution mode drives the production mode (i.e., a module loaded for "test" execution mode provides the override for production mode to "false").
On Tue, Jul 5, 2011 at 4:13 PM, Josh Canfield <[email protected]> wrote: > Can you just use tapestry.execution-mode ? > > http://tapestry.apache.org/configuration.html#Configuration-SettingExecutionModes > > String executionMode = > System.getProperty("tapestry.execution-mode", "production"); > > Currently TapestryFilter is only pulling it from system properties, > but the SymbolProvider I recently added for pulling additional modules > from the command line could be used instead (it's defined directly > above the call looking for execution-mode. > > Josh > > On Tue, Jul 5, 2011 at 3:36 PM, Igor Drobiazko <[email protected]> > wrote: >> Currently a Tapestry app can run either in production mode or not production >> mode (let's say test mode). Frequently this true/false decision is not >> sufficient. For example, we have three different environments the >> application is deployed to: test, integration and production. So a >> three-value decision is needed. >> >> I would like to deprecate the tapestry.production-mode symbol in favour of >> tapestry.app-mode. The new symbol would take one of the values "test", >> "integration", "production" (let's say a enum Mode). Any objections? >> >> -- >> Best regards, >> >> Igor Drobiazko >> http://tapestry5.de >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
