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]