If T5 could throw more specific exceptions, as oppose the generic ones that it does, then it'd be a simple exception handling matter for the user to decide what to do. (As mentioned above.)
I rose a JIRA about this last year: Throw bespoke exceptions so they may be more easily identified by Error Handlers https://issues.apache.org/jira/browse/TAP5-1733 Steve. On 29 August 2012 19:20, Lance Java <lance.j...@googlemail.com> wrote: > It sounds like you are fixing something that really should be handled by > tapestry. I agree that a 404 is much better than a 500 in these cases and I > think it should be the default behavior. > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/How-to-return-HTTP-404-for-in-exact-URL-requests-tp5715875p5715876.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
