Actually it seems Wicket is to blame here. In wicket-ajax.js, line 1680 (processScript() method) there is the following line: var req = new Wicket.Ajax.Request(src, onLoad, false, false); where src is the src attribute of the contributed script element.
Why Wicket tries to load the script body with Ajax and add it as <script> body here </script> to the <head> ? It seems to be much more simpler just to add the contributed <script src="..."> to the <head>. On Thu, Sep 22, 2011 at 11:23 PM, Pointbreak <pointbreak+wicketst...@ml1.net> wrote: > Of course you could also just load the scripts in your page instead of > via ajax... just my 2cnts. > > On Thursday, September 22, 2011 3:18 PM, "Steve Lowery" > <slow...@gatessolutions.com> wrote: >> Is that a filter on my end? Would that go before or after my wicket >> filter >> mapping? Any helpful resources out there on this? I haven't dealt with >> OPTIONS methods before. >> >> >> On Thu, Sep 22, 2011 at 2:28 PM, Steve Lowery >> <slow...@gatessolutions.com>wrote: >> >> > I'm having an issue using resources after an ajax swap, in this case >> > jquery. My home page does not have anything jquery related on it. There >> > is >> > an AjaxFallbackLink which swaps out the main content. The new content >> > Panel >> > has a jquery header contributor. I see this is being returned in the >> > response to the AjaxFallbackLink click: >> > >> > <ajax-response><header-contribution encoding="wicket1" ><