igor.vaynberg wrote: > > i would hate a user to look at a signup form without a signup button > because something inside it caused an error. > > i would also hate to see a user at a checkout page with a missing > $500.00 discount amount shown because there was an error in the > discount label. >
Some forms can be submitted by pressing enter, but anyway, there are indeed cases where removing a small component is not a good idea. It's probably better to replace the whole form or the whole checkout list with an error message, or in some cases replace/redirect the whole page (the current behavior). Anyway, I want to have the option to catch exceptions from child components at certain points that I can define. And I think I got a new idea.. involving replace and RestartResponseException Adrian -- View this message in context: http://www.nabble.com/Handling-exceptions-during-render-tp20301737p20336435.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
