[WICKET-2734] Form#anyComponentError change in 1.4 breaks validation

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 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
• Fix Version/s: 1.4.7, 1.5-M1
• Component/s: wicket
• Labels: Form anyComponentError hasError hasErrorMessage validation wicket
• Environment: wicket 1.4.5
• Assignee: Juegen Donnerstag
• Reporter: Russell Morrisey
• Created: 09/Feb/10 19:52
• Updated: 05/Mar/10 21:56
• Resolved: 11/Feb/10 18:04

Description

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.