do you have a small testcase (unit test case or something)
Because our form example also has some required and others not and that is working fine.

johan


On 3/30/06, jeiess <[EMAIL PROTECTED]> wrote:
having a little trouble with form validation using 1.2-beta2.
here's what i've got:
public final class RegForm extends Form {
. . .
public RegForm(final String id) {

username = new TextField("username", new PropertyModel(properties,
"username"));
username.setRequired (true);
add(username);
. . .
email = new TextField("email", new PropertyModel(properties,"email"));
email.add(EmailAddressPatternValidator.getInstance());
email.setRequired(true);
add(email);

final FeedbackPanel feedback = new FeedbackPanel("feedback");
this.add(feedback);
. . .
}
. . .
}

when i run the app it seems as though the required setting 
for username is being ignored. as long as i provide a value
for email the form is considered valid and onSubmit() processing
is followed. if i remove the required setting on email only then will
the username required setting kick in.

can you guys see any obvious problems here?


View this message in context: setting required on multiple form components
Sent from the Wicket - User forum at Nabble.com.


Reply via email to