Hi, I'm guessing that the markup you are trying to render just before the body tag is a <script> tag that references a JS file (or inlines some JS) that will initialize some JS object. Keeping it at the end of the HTML is just to ensure that the rest of the DOM is fully loaded before this particular JS fires.
When faced with this requirement I generally put the appropriate JS in the HeaderResponse / renderOnDomReadyJavascript() and it has the same effect - you can see an example here: http://ptrthomas.wordpress.com/2009/08/12/wicket-tutorial-yui-autocomplete-using-json-and-ajax/ Your page / component needs to implement IHeaderContributor if not already. Thanks, Peter. On Fri, Sep 4, 2009 at 11:22 AM, Petr Fejfar <petr.fej...@gmail.com> wrote: > Hi all, > > I'm trying to wrap some jQuery plugins as a wicket > component but I met a problems with positions calculated > by jQuery's script in some page layouts controlled by > a mix of absolute and relative DIV's positions. > > Plugin's author recommends to render part of markup > at the very end of markup just before </body> tag. > > How to achieve this in Wicket's component oriented > environment? What would be the best technique? > > > Thanks, Petr > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
