I can kind of see what is going on, the YourApplication class is
loaded using a different classloader then the wicket jar. and tomcat
cleans it up. fair enough. but, YourApplication class extends
Application which is inside the jar, so tomcat should not be cleaning
it up...makes no sense. How can
Ok, I've pinpointed the underlying cause. Indeed, the file is simply
removed before the destroy() method has a chance to clean up. I verified
this by using this ugly hack:
1. Adding a field:
private InputStream wicketJarProtector;
2. In WicketFilter.init() I open the wicket jar to
Hi,
I'm having problems with deployment/undeployment of Wicket apps on
Tomcat (and also JBoss, though I think it's related to the fact that it
embeds Tomcat). Basically, in both cases undeployment comes back with an
Exception, leaving the server in a dirty state and I have to restart
the
I often have the same problem and symptom in my dev Tomcat, forcing me te
restart it.
On Sat, Mar 20, 2010 at 5:06 PM, Alexandros Karypidis akary...@yahoo.grwrote:
Hi,
I'm having problems with deployment/undeployment of Wicket apps on Tomcat
(and also JBoss, though I think it's related to
interesting, wonder why the class would be unloaded *before* the
application classloader.
try this, add a field private PropertyClassResolver resolver=null; to
your application subclass, see if the field is enough to stop the
class from unloading.
-igor
On Sat, Mar 20, 2010 at 9:06 AM,
