Those type of exceptions should be guarded against in your code (with
validators, etc.). You shouldn't typically want to see them in
"production." I don't do anything special to handle unchecked
exceptions for database problems because it's usually one of the
following issues:
1. My code isn't
helps. I really would like to hear from folks here about how to do
the right thing.
Best,
David
--- On Sun, 4/11/10, David Chang wrote:
> From: David Chang
> Subject: How to centrally handle common exceptions from the databsae layer?
> To: users@wicket.apache.org
> Date: Sunday, A
I am hoping to understand how to write a good wicket app regarding handling
exceptions from the databsae layer?
For a wickt form, I can have the following to handle user submission:
@Override
protected void onSubmit() {
User u = getModelObject();
userDao.saveUser(u);
setResponsePage(Resul
