Dmitry, >From an example in an earlier post on this list, I use the approach of having:
configuration.add(SymbolConstants.PRODUCTION_MODE, "true"); in my AppModule, so that by default production mode is always set to true for deployments, and then for any run/debug configurations in the developer's IDE, just override that setting with the VM argument: -Dtapestry.production-mode=false This means you will never need to set it for a release as the default is "true". Hope this helps. Regards, Jim. -----Original Message----- From: Dmitry Gusev [mailto:dmitry.gu...@gmail.com] Sent: 27 August 2010 08:54 To: Tapestry users Subject: Blog post about T5 exception handling on GAE FYI http://dmitrygusev.blogspot.com/2010/08/gae-and-tapestry5-exception-handling .html One thing I'd like T5 have though is something like in RemoteOnly mode in ASP.NET. http://msdn.microsoft.com/en-us/library/h0hfz6fc.aspx RemoteOnly Specifies that custom errors are shown only to the remote > clients, and that ASP.NET errors are shown to the local host. This is the > default value. So that even if I debug application in production mode I could get detailed exception report and not production one. Now I have to use development mode to debug (or consult with logs), but then I often forgetting to switch back to production mode prior to deploy. Can anybody share his practice of switching production mode on/off during development cycle? -- Dmitry Gusev AnjLab Team http://anjlab.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
