Caused by the use of <wicket:head> in a child page without
<wicket:extend> in the body. I'm going to file a bug report against the
misleading error message.
Gili
Gili wrote:
Has something changed in Wicket 1.2 for header contribution? I was
under the impression that if an inheriting page had both <head> and
<wicket:head> then Wicket would copy only the contents of <wicket:head>
up to the parent and the rest of the content of <head> is purely for
previewability purposes and is discarded at runtime.
For an unknown reason, I am getting an exception when rendering a
page where Wicket is complaining I define a component in the markup bu
never add()ed it in the Java code. But I have!
I suspect something in the header contribution code is screwing
things up because if I remove <wicket:head> so that the component is
available directly in <head> then add() works fine with no error. Ideas?
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
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
