myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Kienenberger (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3547) Can't use expression for validator attributes
Date Wed, 16 May 2012 18:51:07 GMT


Mike Kienenberger commented on MYFACES-3547:


Are you sure that the attribute pattern used in DateTimeConverter will allow a *validator*
to evaluate the attribute expression at render-time?   I had been using this very pattern
for years, but found it ineffective for anything other than build-time evaluation two days
> Can't use expression for validator attributes
> ---------------------------------------------
>                 Key: MYFACES-3547
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.1.7
>         Environment: validator ajax
>            Reporter: Deryk Sinotte
>            Priority: Minor
>         Attachments:
> Attaching a test case that shows a problem when using an expression for an attribute
in a validator. We have markup that looks like this:
> <h:inputText id="ajaxMy"
> value="#{testBean.myNumber}">
> <f:validateLongRange minimum="1"
> maximum="#{testBean.maxValue}"/>
> <f:ajax execute="@this"
> render="@form"/>
> </h:inputText>
> When the value of the maximum attribute is modified via Ajax from another input field,
the value of the bean is properly set but the validator doesn't resolve appear to resolve
the expression at the right time and the result is that validation occurs against the "old"

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message