It's not a wicket issue. When Tomcat has to access resources in a jar file of a web app, it may lock it. Another attribute your can try is antiJARLocking, which is a little "nicer" than autiResourceLocking. You really only need to set these attribute if you do hot redeployment, e.g. in a development environment. In a production environment where you will stop the server before undeployment, it doesn't really matter.
Yuesong -----Original Message----- From: Sébastien Piller [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 3:29 AM To: [email protected] Subject: Re: Problem on undeploy 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
