The docs say this: If the tapestry.execution-mode is not declared, Tapestry will automatically look for the tapestry.production-modules parameter, because "production" is the default tapestry.exection-mode value.
So the execution mode should be production since I didn't set is explicitly? Or do I still need something in web.xml to get this effect? ----- Original Message ----- From: Dmitry Gusev To: Tapestry users Sent: Wednesday, June 12, 2013 4:44 PM Subject: Re: symbol not defined Just set the value of the symbol, try adding this via system properties: -Dtapestry.execution-mode=production On Wed, Jun 12, 2013 at 7:41 PM, George Christman <gchrist...@cardaddy.com>wrote: > It's funny you ask this question, I was just about to ask a similar one > about getting production mode. > > > On Wed, Jun 12, 2013 at 11:28 AM, John <j...@quivinco.com> wrote: > > > This code blows up on production system, but is fine on dev and qa! How > > should I fix it? > > > > John > > > > /** The execution mode. */ > > @Inject > > @Symbol(SymbolConstants.EXECUTION_MODE) > > private String exeMode; > > > > org.apache.tapestry5.ioc.internal.OperationException: Symbol > > 'tapestry.execution-mode' is not defined. > > > > > -- > George Christman > www.CarDaddy.com > P.O. Box 735 > Johnstown, New York > -- Dmitry Gusev AnjLab Team http://anjlab.com
