Hi,
For wicket-examples'
http://www.wicket-library.com/wicket-examples-6.0.x/ajax/effects<http://www.wicket-library.com/wicket-examples-6.0.x/ajax/effects?1>
all
I had to do was to add
@Override
public void renderHead(IHeaderResponse response)
{
super.renderHead(response);
response.render(OnDomReadyHeaderItem.forScript("jQuery.noConflict();"));
}
to the page that uses Prototype (EffectsPage.java).
But it is quite simple demo so maybe more work is needed in a real use case
like yours.
On Mon, Nov 12, 2012 at 2:58 AM, Marcin Zajączkowski <msz...@wp.pl> wrote:
> 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 new JavaScriptBundle which bundle it with the original one
> - set a jQueryReference to my bundle
>
> Is there any simpler way to do that? There is probably more people
> facing with that problem and some build in solution which be useful.
>
> Regards
> Marcin
>
> --
> http://blog.solidsoft.info/ - Working code is not enough
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>
