[
https://issues.apache.org/jira/browse/WICKET-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519616
]
Jan Kriesten commented on WICKET-842:
-------------------------------------
IMHO the problem is, that you don't always know what the parent defines. So
when you extend a page class, you should always be able to add components
without knowing what structure has been defined yet.
<html> (and maybe <head> and <body>, too) are special tags in that matter. They
are taken as given when not specifically defined with a wicket:id. You
automatically add to them - and they're generated for you if not defined. No
other tags are generated by wicket, so in that respect they're outstanding
anyway.
> <html wicket:id="html"> is broken again...
> ------------------------------------------
>
> Key: WICKET-842
> URL: https://issues.apache.org/jira/browse/WICKET-842
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Environment: JDK 1.6 / OpenSuSE 10.2
> Reporter: Jan Kriesten
> Attachments: test.tar.gz
>
>
> hi,
> some changes in latest trunk broke adding a wicket:id to <html> again! :-(
> actually, the wicket:id in <html> works. but extending such a basepage and
> then
> adding a component to it doesn't work any more! the component hierarchy
> doesn't
> seem to be resolved correctly.
> test case is attached.
> regards, --- jan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
