The Include tag is very raw indeed. Ideally it would be more like Sitemesh (but without the XML configuration and without it being a filter) in that it actually parses what it recieves, and tries to clean up/ merge/ etc. There's a big note about this in the comments.
It's something I'd like to build in sometime, but will not have time for in a short term. Any help is appreciated, so if anyone is fluent in this field... Would you mind adding an RFE for this. Eelco On 9/9/05, Shekhar Jha <[EMAIL PROTECTED]> wrote: > Wicket 1.1B3 > > I am trying to use the wicket.markup.html.include.Include to include a > relative URL in to the webpage. But it seems that during page rendering, the > > generated page contains the page generated by URL as a single blob. Even > though the browser renders the page properly, the page source is not > asthetically clean with single <head>, <body> tag as expected. > > Is this the expected behaviour of the Include tag or can a choice of proper > > Model help w.r.t. this? > Thanks for your input, > sjha > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
