public class WicketApplication extends WebApplication
{
@Override public void init() {
this.getMarkupSettings().setStripXmlDeclarationFromOutput(true);
}
}
On Wed, Apr 16, 2008 at 3:06 AM, <[EMAIL PROTECTED]> wrote:
> Hi:
> It took me a while to find out why my iframe was not displaying properly.
> I have a parent/container page like
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> <html xmlns="http://www.w3.org/1999/xhtml"; xmlns:wicket="
> http://wicket.apache.org/";>
> ...
> <wicket:child>iframe child</wicket:child>
>
> and the child page is like
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> <html xmlns="http://www.w3.org/1999/xhtml"; xmlns:wicket="
> http://wicket.apache.org/";>
> ...
> <wicket:extend>....
>
> The final rendering the html page would contain <?xml.> declaration ,
> which results in improper display in browser. Once I remove the <?xml..
> line from the child html file, the final rendering of html
> does not show <?xml line, i.e. the first line is <!DOCTYPE..., and this
> somehow make the browser happy and display the page correctly.
> My understanding is that for child page, wicket would discard anything
> outside <wicket:extend>, but apparently, the presence of <?xml as the
> first line in child html somehow forced the parser to add the <?xml to the
> final html output as the first line, which also surprises as I thought
> wicket would stream out content as it goes instead of waiting to parse the
> entire tree.
>
> Thanks
>
