Hello, I had some same interrogations as Matej has ...
I'm currently trying to fully reimplement a complex form made in struts in wicket, and some buttons of the form are there only to dynamically add elements to a list (doing a roundtrip with the server), but don't have to trigger the validation stuff. But that's what's done, and it's a bit annoying. > Why can't use just use a model for this? I agree with you, model should be updated, I think at Wicket models as View models. But the idea of Matej of not immediately storing in the real model could be a good idea (but not done in the invalid data field). What could be great is to register / inform the Form which buttons may trigger the validators/model updating of the components, and which buttons may not. Regards, -- Laurent ------------------------------------------------------- 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
