*package *org.apache.wicket.settings;

*import *org.apache.wicket.ajax.WicketAjaxDebugJQueryResourceReference;
*import *org.apache.wicket.ajax.WicketAjaxJQueryResourceReference;
*import *org.apache.wicket.ajax.WicketEventJQueryResourceReference;
*import *org.apache.wicket.request.resource.ResourceReference;
*import *org.apache.wicket.resource.JQueryResourceReference;
*import *org.apache.wicket.util.lang.Args;



*/**  * Class for settings related to the JavaScript libraries that come
with and are used by Wicket.  * **<p>*

*  * With these settings the user application can replace the JavaScript
libraries used for Wicket's  * event and Ajax functionality. By default
Wicket uses {**@linkplain *



*JQueryResourceReference JQuery}  * as a backing library but via this
interface the application can replace the implementations of  *
wicket-event.js, wicket-ajax.js and wicket-ajax-debug.js to use
implementations on other  * libraries, such as YUI or DOJO. The resource
reference implementations need to specify the  * {**@linkplain *

*ResourceReference#getDependencies() dependency} on the backing library, if
needed.  *  * **@since *

*6.0  */ **public class *JavaScriptLibrarySettings


Class it is there on my 7.3.0

On Fri, Aug 12, 2016 at 11:00 AM, Tom Götz <[email protected]> wrote:

> Hi there,
>
> I am currently migrating a webapp from Wicket 6.x to Wicket 7.3 (can’t use
> 7.4 due to a bug that hits us —> other topic).
>
> When clicking on some ajax link, I get the following stacktrace:
> https://gist.github.com/tgoetz/809196f35be40157d7c69d1879871d43
>
> I don’t know yet what exactly causes this, but has anybody maybe seen that
> already? I am especially worried about the package
> def.JavaScriptLibrarySettings, which does not seem to exist?! Plus: how
> could that class not be found, as it’s part of wicket-core?
>
> Any hints welcome!
>
> Cheers,
>    Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Regards - Ernesto Reinaldo Barreiro

Reply via email to