thats not for classes. Wicket doesnt have by default (there are some
solutions) a class reloader
What you see is for for the markup files (and we also do that for other
resources)
johan
On Thu, Jul 17, 2008 at 10:05 AM, [EMAIL PROTECTED] wrote:
As always, excellent feedback- a HUGE thank you
Hi
After starting my local Webpshere Application Server (6.1.0.15), running my
wicket application (1.3.4) in development mode, the ModificationWatcher
appears to devour memory, until eventually I get out of memory exceptions
(when my latest exception occured, my wicket instance was using 1.7GB
wicket has special support for that:
if (urlConnection instanceof JarURLConnection)
{
JarURLConnection jarUrlConnection =
(JarURLConnection)urlConnection;
URL jarFileUrl = jarUrlConnection.getJarFileURL();
