Sven: I'm not privy to participate in deployments and I don't have
access to server setup. One thing is certain it was a very interesting
situation because another wicket application was running just fine on
the same server. (That's how I diagnosed the deployment issue - the
other appRoot would giv
Hi!
> 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
Interesting. It might be related to:
http://apache-wicke
Thanks Dave, that's a good advice.
Just out of curiosity: what did go wrong with your deployment?
Best,
Sven
On 25.06.2011 04:26, D D wrote:
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]/ap
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
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
201
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 peop
