Craig McClanahan wrote:
The "validator" attribute has been there since JSF 1.0 ... it
corresponds to the getValidator() and setValidator() methods of the
EditableValueHolder interface. In a similar way, the "converter"
attribute has been around since JSF 1.0 on components that implement
Value
On 1/3/07, Simon Kitching <[EMAIL PROTECTED]> wrote:
Thanks David.
Is this "validator" attribute something added in JSF 1.2? I'm sure it
doesn't exist in JSF 1.1 (which is what MyFaces 1.1.x supports).
The "validator" attribute has been there since JSF 1.0 ... it corresponds to
the getValida
nt association in lieu of directly
inspecting the
> local bean properties? For a hint, look at the prior lifecycle figures.
> Don't worry if you can't quite figure it out right now; we'll
explain it all
> at the end of the article.
>
> Why, if a validation method
rectly inspecting the
> local bean properties? For a hint, look at the prior lifecycle figures.
> Don't worry if you can't quite figure it out right now; we'll explain it all
> at the end of the article.
>
> Why, if a validation method is actually part of a backing b
ually part of a backing bean, must its
value be generically evaluated with a component association?
The trick here is that, although the validateEmail inline validation method
is part of the actual backing bean, the method must reference the value via
component association rather than accessing the
ent association?
The trick here is that, although the validateEmail inline validation method
is part of the actual backing bean, the method must reference the value via
component association rather than accessing the local properties directly.
Because validation occurs before the component values are bound
6 matches
Mail list logo
