[
https://issues.apache.org/jira/browse/WICKET-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538392
]
Igor Vaynberg commented on WICKET-1108:
---------------------------------------
i have built some apps with pretty darn complex ui and it has never been an
issue. realize that not all work is done in constructor, only the setup of the
component hierarchy whose lifecycle spans the constructor. if situation is too
dynamic to be done in constructor then it can easily be done in
onbeforerender() and for a two phase init you can do:
onbeforerender() { if (!hasbeenrendered()) { // TWO PHASE INIT }}
> Inherited Pages don't include components from super page.
> ---------------------------------------------------------
>
> Key: WICKET-1108
> URL: https://issues.apache.org/jira/browse/WICKET-1108
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Reporter: Brill Pappin
> Assignee: Igor Vaynberg
> Fix For: 1.3.0-beta5
>
> Attachments: test-wicket-1108.zip
>
>
> I've got two pages:
> an abstract base page that has items included in all pages (BasePAge in this
> spike), and a concrete page (Index in this spike):
> - BasePage includes items like the title
> - Index only has content that applies to the index page.
> What I expected to happen was that the BasePage would include its components
> and the index page would include its one component.
> However when run, I get an error that not all the wicket tags have components.
> This was unexpected and counter intuitive to a java developer.
> Of course, being very new to Wicket, I may simply have done something wrong
> (which is why this is not marked as a bug).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
