Agreed. I thought you were talking about a form on an already built page. Sorry.
Gili Phil Kulak wrote:
If I can't even render the page, how am I supposed to prompt the user for better input? And if this were a form on an already built page, promting the user for better input would be recovering. Not recovering would be showing a stack trace or a generic message that just says "There's been a problem. Too bad for you." On 8/7/05, Gili <[EMAIL PROTECTED]> wrote:The same way you react with the JRE throws NumberFormatException: you get back to the user and tell him his input was invalid. I don't think you're supposed to "recover" here as much as realize the user input was invalid and reprompt him for good input. Gili------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
-- http://www.desktopbeautifier.com/ ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
