* Apaar Trivedi:
> I understand that if my app is in deployment mode then all run
> time exceptions, including anything which happens during an Ajax
> request will be caught by my RequestCycle.onRuntimeException,
> and this is working fine. But how can I replicate this behavior
> during development mode? During development mode my ajax
> runtime exceptions merely show up in my Tomcat console, and do
> not forward to the error page.
This is fixed already, see:
Use standard exception handling in AjaxRequestTarget
http://issues.apache.org/jira/browse/WICKET-313
However I didn't notice different behavior between deployment and
development when I had this problem.
> Also, how can I conceivably handle these errors on the client
> side, say for instance I experience an ajax runtime error during
> some request and I would like to display a friendly message in
> my window, instead of forwarding to the error page, how can this
> be done?
Just define wicketGlobalFailureHandler() JS function in your document.
There is a plug-and-play implementation for Dojo here FYI:
http://wicket-stuff.svn.sourceforge.net/viewvc/wicket-stuff/branches/wicket-1.3/wicket-contrib-dojo/src/main/java/wicket/contrib/dojo/markup/html/floatingpane/AjaxErrorBehavior.java?revision=1755&view=markup
Cheers,
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
