On Friday 16 Dec 2005 14:27, Igor Vaynberg wrote:
> i think it is reasonable that wicket
> catches all runtime exceptions that originate within its ui-tier. it needs
> to do that in order to show an error page. if it lets the exception go then
> what is responsible for showing the error page?
I agree, wicket should catch all uncaught exceptions. It would also be nice
(eg for hibernate transaction handling) if it were possible to allow wicket
applications to also catch exceptions.
The small refactoring I suggested below does not change wickets handling of
exceptions at all. It simply lets wicket applications override a non-final
method to catch exceptions etc.
> >
> > for example, if Request cycle had a non-final method:
> >
> > protected void doRequest() throws RuntimeException
> > {
> > // Attach thread local resources for request
> > threadAttach();
> >
> > // Response is beginning
> > internalOnBeginRequest();
> > onBeginRequest();
> >
> > // If request is parsed successfully
> > if (parseRequest())
> > {
> > // respond with a page
> > respond();
> > }
> > }
> >
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
