Hi Stefan, as far as I understood markup inheritance correctly, the xml and doctype of B is ignored and only the part that is specified inside the <wicket:extend>...</wicket:extend> tags is taken over in A instead of the <wicket:child>...</wicket:child> part. Everything that is specified additionally in B is only for previewing B in a browser of your choice. So the answer to your question is 1.
Wolf Am 11.05.2010 08:09, schrieb Stefan Lindner: > Dear Wicket wizzards, > > given is a page A with a HTML file that has no doctype, just starting with > <html>...<wicket:child> > > The Page's class is extended by B and the markup of B has a proper HTML file > with XML and doctype lines. > > What is the intended behavior of wicket? > > 1. Ignore the exdending B's xml and doctype an use the settings form A > 2. Override the settings from A with the proper doctype from B > 3. Control it in Wicket's Application.init()? > > getMarkupSettings().setStripXmlDeclarationFromOutput(true/false) has no > effect. In my case (given A that cannot be modified) item 1. is true. > > Stefan > > > > > > --------------------------------------------------------------------- > 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]
