Hello, > I think youre usecases can be build now with the current code base. > uc1: that new button should be an immediant button (this is a property) then > the model values are not processed.
By the time, I don't really understand the "immediant" term, doesn't seem to be an english term at all (trusting my dictionary). > uc2: you just have to validate this in the button i talked above (if text > field is filled in yes or no) What I don't like in this solution is that it is not general enough : I can not benefit from the "out of the box" first level Validators for validating the monkey name : what if I need some pattern matching, or if it must be an Integer, ... What I would prefer, and that could be more general, would be a mean to associate the validation (and model updating !) of some parts of the form to the general form submitting buttons, ... and associating other parts of the form to other actions. Thus being able to group area of concerns ... ------------------------------------------------------- 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
