[WICKET-6543] onConfigure() Javadoc claims Overrides must call super, but there is no check to enforce it

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 8.0.0-M8
• Fix Version/s: 8.0.0
• Assignee: Sven Meier
• Reporter: Kees van Dieren
• Created: 05/Mar/18 13:08
• Updated: 29/Mar/18 21:52
• Resolved: 29/Mar/18 16:37

Description

https://github.com/apache/wicket/blob/9e42a9548adb0da540e4e87d491f5824e778537e/wicket-core/src/main/java/org/apache/wicket/Component.java#L795 claims that: 

Overrides must call {@code super.onConfigure()}, usually before any other code

However Component#onConfigure() does not set a flag (like onInitialize() does) nor does configure() check that its own onConfigure() gets called.

As user of the framework, I would expect consistent behavior between onConfigure() and onInitialize().

It might be a good idea to fix this before Wicket 8.0.0, as changing this behavior is a breaking change.

Issue Links

• mentioned in: Page Loading...