In the current WWB strategy, required fields are enforced in your model/DAO layer. For example, if you click your "Save" action, the action on your page would be invoked. This, in turn, calls your DAO or model. Often fields are conditionally required based on use case and or data conditions. We're currently using the Spring validation framework to validate required fields on the bean via the DAO. In turn, messages are returned back to the page and we add them to the Wicket feedback via the error() method.
However, it would be a fairly simple matter to add a "required: true" parameter for times when you know that a field will always be required. I'll add this to the features requests in sourceforge. -Dan On 9/15/07, Zenrique Steckelberg <[EMAIL PROTECTED]> wrote: > > > How can I make one textfield required? Couldn't find it anywhere in the > docs. > Besides that, I susggest you put the JavaDocs somewhere in the framwork > site > too. > > Thanks in advance! > -- > View this message in context: > http://www.nabble.com/Re%3A-Wicket-Web-Beans-1.0-rc1-Released-tf4431603.html#a12691422 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
