Re: Ability to simply enable jQuery.noConflict() globally for an application in Wicket 6

Thanks Martijn for your replies. I have just found them. On 2012-11-13 13:23, Martijn Dashorst wrote: > If you don't have a common base page for all your pages, then you can > use a ComponentInstantiationListener that adds a behavior to all > pages, rendering the specific javascript invocations. >

Re: Ability to simply enable jQuery.noConflict() globally for an application in Wicket 6

Hi, For wicket-examples' http://www.wicket-library.com/wicket-examples-6.0.x/ajax/effects all I had to do was to add @Override public void renderHead(IHeaderResponse response) { super.renderHead(response); response.render(OnDomR

Ability to simply enable jQuery.noConflict() globally for an application in Wicket 6

Hi, I have an application which internally uses prototype. After migration from Wicket 1.5 to 6 I had problems with conflicts. It helped to enable non conflict mode in jQuery, but to do this globally I had to do a few things: - an one line script - a corresponding JavaScriptResourceReference - a