[
https://issues.apache.org/jira/browse/WICKET-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1108.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: 1.3.0-beta5
this is a bug in your BasePage. the common init method you are talking about
should be inside your basepage and used by both constructors there. this has
nothing to do with wicket.
if you talk about this in context of making this kind of change in wicket it
would mean having a "two-phase init", which is a pattern that deals with this
and other usecases. the big downside to that pattern is that you have to
transfer all your constructor arguments into fields so they can be accessed by
the second phase' init method, and for a framework concerned with size of the
objects this does not mesh very well. it also adds a lot more code you have to
write. so as far as making this change in wicket i do not think we will do
that. it is simple enough to add a private init() into your basepage and
forward both constructors to it.
> 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.
