[
https://issues.apache.org/jira/browse/MYFACES-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277012#comment-13277012
]
Mike Kienenberger commented on MYFACES-3547:
--------------------------------------------
Leonardo,
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 ago.
> Can't use expression for validator attributes
> ---------------------------------------------
>
> Key: MYFACES-3547
> URL: https://issues.apache.org/jira/browse/MYFACES-3547
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.1.7
> Environment: validator ajax
> Reporter: Deryk Sinotte
> Priority: Minor
> Attachments: validator.zip
>
>
> 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" values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
