Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
8.0.0-M8
-
None
-
None
Description
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.
Attachments
Issue Links
- mentioned in
-
Page Loading...