[
https://issues.apache.org/jira/browse/WICKET-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831651#action_12831651
]
Juergen Donnerstag commented on WICKET-2734:
--------------------------------------------
please provide a junit test case for us to validate possible patches and to
make sure future changes to Wicket core don't accidentially change the
behavior. Thanks a lot.
> Form#anyComponentError change in 1.4 breaks validation
> ------------------------------------------------------
>
> Key: WICKET-2734
> URL: https://issues.apache.org/jira/browse/WICKET-2734
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-M1, 1.4-M2, 1.4-M3, 1.4-RC1, 1.4-RC2, 1.4-RC3,
> 1.4-RC4, 1.4-RC5, 1.4-RC6, 1.4-RC7, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5,
> 1.4.6
> Environment: wicket 1.4.5
> Reporter: Russell Morrisey
>
> In wicket 1.4, Form#anyComponentError was changed so that it only calls
> hasErrorMessage() on instances of Form or FormComponent. This is a
> validation-breaking change. Currently, when Component#error(...) is called
> for any component which is neither a Form nor FormComponent, the error is
> ignored by a Form#hasError() check on the form containing this component.
> Please change it back to check any Component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
