I get that. My point is that setting up execution mode for development renders contribution for PRODUCTION_MODE useless.
On Thu, Mar 19, 2015 at 3:39 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Thu, 19 Mar 2015 09:46:25 -0300, Adam X <vbgnm3c...@gmail.com> wrote: > > So the confusing part is that in order for Tapestry to use the >> DevelopmentModule which has the necessary configuration it is required to >> pass a JVM parameter in the first place, which in turn yields the point >> about adding: >> >> configuration.add(SymbolConstants.PRODUCTION_MODE, false); >> >> kind of pointless. So my question is, what is the point of the above, if >> in order to force the development module it is necessary to pass a JVM param >> in the first place? >> > > I don't think you got why execution modes exists. It's for having > different configurations for different environments (development, QA, > staging, production, etc) which you can select by JVM argument. It defaults > to the production environment, so you don't accidentally use the wrong > configuration in user- or client-facing environments. > > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
