Did somebody create a jira issue already? I'm experiencing the same log statement since upgrading to 1.3.4.
Perhaps the fix for Wicket-1636 is the reason why the header check was never performed previously? I have <head> and <body> in my page's markup. Sven igor.vaynberg wrote: > > quickstart and jira please > > -igor > > On Mon, May 26, 2008 at 10:54 AM, Jan Kriesten > <[EMAIL PROTECTED]> wrote: >> >> Hi Igor, >> >>> are you sure the markup of the child page that you are trying to >>> render is inside wicket:extend tags? >> >> yes, I am. And also the application didn't show this behavior before with >> trunk from two days ago... >> >>> what happens if you remove the transparent resolver, does the error go >>> away? >> >> Yep, when I remove it, the error is gone. >> >> --- Jan. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/WebPage-markup-error-with-latest-trunk-tp17467363p18087509.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
