onInitialize javadoc should mention heirarchy issues,
------------------------------------------------------
Key: WICKET-3020
URL: https://issues.apache.org/jira/browse/WICKET-3020
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 1.4.10
Reporter: Pranav Kacholia
As far as i can tell, if you have an heirarchy of components, and one of the
parents has an add(component) called in its constructor then the timing as to
when onInitialize is called, is no longer predictable. It may be that rendering
will start before the child component has finished intializing (the constructor
has finished being called).
so if you want a more predictable rendering, (with all the child components
being constructed first), you would need the whole heirarchy to use
onInitialize and none of the parents should call add(component) in its
constructor.
This should be mentioned in the javadoc, or somewhere.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
