Hello,
Yes, I did, realizing that it's a bit of a coarse solution. As it happens,
my application main function is to execute scripts for automated deployment
on a WebSphere platform, so users work with a JEE-application they select
from a wicket Ajax-textfield with application build versions
Hi,
On Sat, Nov 12, 2011 at 7:15 PM, hfriederichs h.friederi...@ohra.nl wrote:
I solved the issue by many trial and error sessions. Maybe I can spare
someone else this ordeal.
In Firefox an Chrome it now works as in IE, by adding this statement in the
init() of my WicketApplication:
I solved the issue by many trial and error sessions. Maybe I can spare
someone else this ordeal.
In Firefox an Chrome it now works as in IE, by adding this statement in the
init() of my WicketApplication:
getResourceSettings().setDefaultCacheDuration(Duration.NONE);
Regards, Hans Friederichs
Made a quick start, but couldn't reproduce the issue, it worked in FireFox...
Be it on a Jetty-server, and I have to cope with WebSphere...
Well, I'll strip my application down to the essentials that I have in the
quick start, and then build up one by one, I guess.
Many thanks, so far!
--
