Frank Silbermann schrieb:
Frank Silbermann schrieb:
[...]
It seems reasonable to want to use the same HTML page to mark up many
Wicket page objects sharing the same layout. Yes, I realize we can
group common HTML in a reusable panel (though we would still need a
trivial HTML file to contain the panel for each Wicket page), and I
realize we can write a single generalized Wicket page and change the
contents of the model.
Timo Stamm schrieb:
Or you could use inheritance.
If I have a long inheritance chain descended from
wicket.markup.html.WebPage, what is the rule as to which class-name
needs to match the HTML filename? Would it always be the class which
inherits from wicket.markup.html.WebPage directly?
AFAIK, wicket loads markup for the current class at first. It will
ascend through the inheritance chain until a markup file is found. If
the markup contains a wicket:extends tag, the markup enclosed in the
wicket:extend tag will be included in the markup of the parent class (at
the location of the wicket:child tag).
I guess it is possible to use more than one wicket:extends tag in an
inheritance chain, but I have not yet been in a situation where it would
have been useful. This is absolutely enough for my needs:
- abstract base pages (access check, context objects)
- pages with base markup (navigation types)
- pages with extending markup (forms, lists)
Timo
(Wie kennt man ob man "schrieb" oder "hat geschrieben" benuetzen soll?)
Habe ich noch nie verstanden, aber hier sollte es sowieso eher "wrote"
sein :)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
