For all poor souls that may run into this problem here is a sanity check to consider.
Attempt to run the following URL: http://yourmachinename[:port]/appRoot/resources/org.apache.wicket.ajax.WicketAjaxReference/wicket-ajax.js Your browser should attempt downloading a file (in case of IE6 - that's the default behavior) If you get error the problem in all likelihood lies with broken deployment - which is pretty interesting in our case since the app rendered on server side without issues but failed on the front end. I hope it helps. Thanks, Dave On Fri, Jun 24, 2011 at 2:41 PM, Martin Makundi <[email protected]> wrote: > Hi! > > It will probably cost you quite some time but you can debug the order > of js library references being loaded in various situations. > > Wicket is a javascript reference to the wicket js methods and if > "Wicket" is undefined it means it is not loaded at that time... for > some reason. > > ** > Martin > > > 2011/6/24 D D <[email protected]>: >> Hello, >> >> We have an issue where IE6 loads and works fine with wicket's js >> during development. As soon as we moved app to "community" server IE6 >> comes up with an error: >> >> "Error: 'Wicket' is undefined >> >> As much as we would wish to get off IE6 we have to stick with it for a >> little longer. I've seen people having issues after moving from 1.4.7 >> to newer version. I've never seen resolution to a thread that we >> running back in Nov. 2010. >> >> Does anyone have any idea what could have gone wrong? >> >> Thanks, >> Dave >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
