On 7/26/07, Federico Fanton <[EMAIL PROTECTED]> wrote: > Hi everyone! > I was wondering if there's a "best practice" for handling exceptions in a > Wicket application.. I'm implementing an IDataProvider for a DataView, and I > see that this interface doesn't throw any exception, so I'd guess that if > something happens inside - say - iterator() that throws an exception, it > should be wrapped inside a RuntimeWicketException... Am I right? > I tried the wiki, Google and "Pro Wicket" but couldn't find an answer.. ^^;; > Many thanks in advance
For maximum flexibility, provide a custom request cycle and override onRuntimeException. Wicket 1.3 only though. For Wicket 1.2 you either have to do with setting an error page that is useful for you, or provide a custom request processor implementation (which is quite an ugly thing to do in 1.2, but possible). Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ IMPORTANT NOTICE: This mailing list is shutting down. Please subscribe to the Apache Wicket user list. Send a message to: "users-subscribe at wicket.apache.org" and follow the instructions. _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
