Hi Michael, This requirement does sound a bit odd to me. To me, the primary role for a validator is to determine whether the data is safe to push into the model. Why would you want to bypass that kind of check in any circumstance?
Regards, Simon On Fri, 2007-10-19 at 10:51 -0400, Simon Lessard wrote: > Hello Michael, > > You could add the check directly inside the validate method to see if > the validation should occur or not. Also since validators aren't > visual artifacts, rendered would not be very semantically correct. > However, I guess a "relevant" or "active" attribute could have been > considered, but that would imply some specification changes to work > with every validators and component libraries. > > > Regards, > > ~ Simon > > > Regards, > > ~ Simon > > On 10/19/07, Michael Heinen <[EMAIL PROTECTED]> wrote: > Is there any reason why validators don't have a rendered > attribute? > > I use a dataList to render a List of fields dynamically and > want to add a validator to an input field depending on an EL > expression. > > > > I found some old discussions in the list about optional > validators but did not find detailed info. > > > > How can I accomplish this without without doubling the outer > input fields? > > > > > > Michael > > >
