ache.org
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 simp
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 PRO
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
="true" docBase="servlet"
> antiJARLocking="true">
> </Context>
>
>
--
View this message in context:
http://www.nabble.com/Problem-on-undeploy-tp15477946p15492542.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---
Yes, I made a syntax error... but even with the syntax bellow, the
problem stills...
Sébastien Piller a écrit :
But the problem stills Have I done a syntax error?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Hello,
thank you for your answer. I wrote a */META-INF/context.xml* file with
that in it:
antiJARLocking
true
But the problem stills Have I done a syntax error?
C S a écrit :
Have you tried the antiLocking options (antiJARLocking and
antiResou
Have you tried the antiLocking options (antiJARLocking and
antiResourceLocking)?
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html I haven't but
they seem to speak to your problem with the left over jars.
--
View this message in context:
http://www.nabble.com/Problem-on-und
Here is a Thread dump from Tomcat (after I have undeployed my app). It
doesn't speak about PageSavingThread, but if anybody see something
wrong
[2008-02-14 12:43:17] [1334 prunsrv.c] [debug] Procrun
log initialized
[2008-02-14 12:43:17] [info] Procrun (2.0.3.0) started
[2008-02-14 12:4
Hello guys,
I have a problem with wicket when I undeploy my application. Tomcat
tries to undeploy everything, but he fails to delete the wicket's API
librairies (wicket-1.3.1.jar, wicket-extensions-1.3.1.jar, etc.).
It seems to the same issue as this one:
http://mail-archives.apache.org/mod_m
