Major Description
As discussed on the devs mail list, the oninitialize method may already be implemented by some user. The Component on the next release can throw an IllegalStateException for those situations. IMO it is better than have this method called twice. I'm sending an patch with the implementation and an test for it.
On a related note, the onInitialize javadoc says:
- Overrides must call super#
{@link #onInitialize()}
. Usually this should be the first thing an
- override does, much like a constructor.
I just put that super call on the onInitialize overriding methods at the ComponentInitializationTest.