---- Michael Heinen <[EMAIL PROTECTED]> schrieb: > A simple example is the dynamic rendering of range input fields. > A validator should be added only to the second field (e.g. dateTo or a > max size) which validates the lower value and the upper value.
Sorry, I don't understand that at all. > Or some input fields could be of type email and should be validated > accordingly but be rendered like other fields. A component representing an email field should have an EmailValidator attached to it, and a component representing something else will not have a validator attached to it. Isn't that completely static information that is known to the page author? Where does "active" come into that? > So there following alternatives: > - use component bindings and add the validators dynamically > - use separate input fields with rendered checks (one with validator and > one without which is ugly) Why would a field sometimes be an email input field and sometimes not? A property in the model (ie the setter method that the value attribute's EL value-expression refers to) will hold either an email or not, won't it? And the EL expression is fixed and refers to just one property, yes? So why isn't it possible to simply define in the page which type of validator is attached to the component? Regards, Simon
