Just like my use case is that I do post processing in a form. The opposite of what you are doing. And thus reversing that logic to facilitate your use case breaks mine.
This is running in circles and we should have a better alternative. I don't think we should reverse the logic, as this in effect means an API break, and potentially a nasty one if people would depend on it and don't read the migration docs (in case of 2.0, for 1.2 an API is out of the question anyway). Eelco > another usecase is where i have a form that has to preprocess some data. i > reuse this form in a lot of places so i would like to encapsulate that > prepreocessing logic in the form's onsubmit which is intuitive, but then i > cant. i have 5 buttons in some cases on this form, so i need to call a util > method on the form from each button which is very ugly. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
