Thanks for your answer guys, I thought this was a issue, I'm going to
try this.
Thanks a lot.
On 19/01/16 10:36, Matías Fernández wrote:
Hello Wicket developers,
I have what I think is a issue but before report it I want to know if
maybe this is a expected behavior. I have been searching in
documentation and Internet about this but didn't found any behavior
like this.
I'm using Wicket 7.1 and I build a page with only a
AbstractDefaultAjaxBehavior's.
Also in this page I have some JQuery plug-ins which need to be loaded
after JQuery is loaded. The problem is the JQuery from Wicket is
loading after all the JS declared on wicket:head tag of the page, the
problem is the plug-in doesn't work if the JS are loading in this
order. The strange behavior is if I add a AjaxLink to the same page,
the JS are loading ok and the page works but the AjaxLink isn't
necessary.
I want to know why Wicket decide to do this in this two situations.
Thanks,
Matías.
