What actual use cases are you thinking of that can't be done by forms? Your idea could be implemented as a special model. I'm not sure what the advantage over the normal form processing is though.
Eelco On 10/11/05, Phil Kulak <[EMAIL PROTECTED]> wrote: > What do you guys think about something like this: you have a model > object with a bunch of setters that take Strings and ints and so > forth, and getters that return complex user types. In the setters > validation and conversion takes place, with a special exception thrown > on failure, the message of which is picked up by Wicket and set on the > component. Comments, questions? > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
