Antoine van Wel wrote:
>
> I think you should prevent that SQLException from happening in the first
> place by validating the form input.
> Then use a FeedbackPanel to display suitable error messages. Just google
> for
> example code with forms, it's basic stuff.
>
> Otherwise, create a FeedbackPanel on your page, put a try .. catch block
> around your sql methods and in case of an exception, write to the
> FeedbackPanel using error("your message")
>
>
I agree with you, catching Runtime exceptions in WebRequestCycle should not
be a part of normal workflow.
I use this thing only to display critical failures information.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/EXception-handling-in-Wicket-tp2340439p2399427.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
