i guess this is a problem of the jvm/jdk itself I guess this is all related to the stupid "i can't close a url connection" thing because i guess it has something to do with the IInitializers lookup that somehowe holds on the something
On Fri, Feb 15, 2008 at 9:29 AM, Sébastien Piller <[EMAIL PROTECTED]> wrote: > Hello, > > I just tried it, and it worked :) I don't know if I can use this > directive on my deployment server... I'll have a look with my hoster. > > After some investigation, I'm now quite sure that it's a Wicket problem. > I tried with a very simple project (Hello World) and it made the lock. > > Could anybody tell me if it's a known bug or if I have to write a jira? > > Thanks > > > TahitianGabriel a écrit : > > Have you also tried the antiResourceLocking=true parameter? > > > > That's the one I use and it works! > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
