Iman Rahmatizadeh wrote:
> Actually the Component.toString() method is somehow heavy, and normally
> any exception thrown in the middle of it would cause bad behavior in
> wicket. Is there a chance to improve this somehow, or make exception
> handling aware of problems that might arise when call
I ran into a problem where wicket(1.2.x) actually swallowed my exception
before reporting it to me and showed another exception. Take this code for
example :
add(new MyComponent("id",new LoadableDetachableModel() {
public void load() {
// do something that throws s
