[
https://issues.apache.org/jira/browse/WICKET-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868862#action_12868862
]
Hudson commented on WICKET-2869:
--------------------------------
Integrated in Apache Wicket 1.5.x #54 (See
[http://hudson.zones.apache.org/hudson/job/Apache%20Wicket%201.5.x/54/])
WICKET-2869 RangeValidator should use getMinimum and getMaximum
Issue: WICKET-2869
> RangeValidator should use getMinimum and getMaximum
> ---------------------------------------------------
>
> Key: WICKET-2869
> URL: https://issues.apache.org/jira/browse/WICKET-2869
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.8
> Reporter: Emond Papegaaij
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.9, 1.5-M1
>
>
> Currently, the RangeValidator uses the fields directly, making it impossible
> to define a dynamic range by overriding getMinimum and getMaximum. Instead of
> using the fields directly, the validator should call these methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
