Wicket currently provides RequestCycle#onRuntimeException with the
full exceptions, including the Wicket wrapped exceptions. Is this
something we should/could improve on?
For instance the thrown exception in this onclick handler:
add(new Link("foo") {
public void onClick() {
throw new RuntimeException();
}
});
will be wrapped twice: first in an InvocationTargetException and that
inside a WicketRuntimeException.
Now I'm not saying there's completely no value in the WRE and ITE, but
to get to the core of what is happening, the onError implementor needs
to go through the whole cause stack to figure out what has happened.
We could at least strip off those wrapper exceptions that were under
control of Wicket: the WRE and the ITE are likely candidates IMO.
WDYT?
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0
