As I see its not the same at all. The exception report behavior is the same only the text is different. Here you are proposing completely different error and behavior in production and in development. Intent is not the same. What if someone intercepts all exceptions and emails production support? Other custom behavior would all be broken.
On Jul 31, 2013, at 11:07 AM, Massimo Lusetti <mluse...@gmail.com> wrote: > On Wed, Jul 31, 2013 at 6:00 PM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: > > I would say no. >> The behavior in production.and development mode differences in general is >> a bad idea. This will preclude valid testing in development. > It would be the same situation of the ExceptionReport page and it would go > hand to hand with the excellent feedback given by the whole framework, > let's read this way: "Hey dev you're accessing page X which doesn't declare > an activation context Y so this is considered an error and will result in a > 404 within production" > > -- > Massimo Lusetti --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
