I'd like to open this (http://www.mail-archive.com/wicket-develop%40lists.sourceforge.net/msg08690.html) discussion again. The argument for keeping StringValueConversionException checked was to ensure the user didn't enter bogus data.  However, as a checked exception, developers are forced to handle this exception on a page-by-page basis, when it could be handled more gracefully, as an unchecked exception, for all pages using Wicket's IExceptionSettings.UnexpectedExceptionDisplay. 

If developers still want to check for and handle bogus data on a page-by-page basis, that option is still available to them. 

Thoughts?  Thanks for your time.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to