use HiddenField instead of a TextField, that way there is no need to disable it.
then the textfield/lookup button can be client-side things that
populate the hidden field.
-igor
On Mon, Aug 3, 2009 at 7:51 AM, nytrus<nytrus...@gmail.com> wrote:
>
>
> egolan74 wrote:
>>
>> 1. If you in control of the input of these disabled fields, why allowing
>> illegal arguments in the first place?
>> 2. If you can't control the entered values, try use FormValidator. With
>> this
>> class, you can create your own Validate logic with the desired fields.
>>
>
> 1. Good observation, but my goal is checking for required fields.
> 2. That's an idea: I can write my class imlpementing IFormValidator and then
> add this to the container form. For checking required fields somethign like
> this could work:
>
> public class RequiredFieldsValidator extends AbstractFormValidator {
> private List<FormComponents> components;
>
> public RequiredFieldsValidator(List<FormComponents> components) {
> this.components = components;
> }
>
> public void validate(Form<?> form)
> {
> for(FormComponent c: components) {
> validateRequired();
> }
> }
> }
>
> --
> View this message in context:
> http://www.nabble.com/Form-skips-validation-for-disabled-not-visible-components-tp24790510p24792189.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
