Hello, > One option is to override Form.process() and compare > findSubmittingButton() against your various buttons, then bypass the > super method if you don't want it to update your model (just return > true). Until wicket has some better way to bypass the model update, this > works just fine.
I can't check it from work today, but I think this solution doesn't work : won't the components not updated be lost when the screen is rendered ? ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
