The thing is, that it's the containers (like Tomcat) that keep the references. We just poll now and then (the frequency), but in the mean time there is no reason that the resources couldn't be released.
Eelco On 9/27/05, Dan Gould <[EMAIL PROTECTED]> wrote: > Thanks Francis, I'll give that a try. Is there any reason why > getSettings.setResourcePollFrequency() should create tons of open > references to wicket.jar? I don't know if it's an expected behavior or > not, but if it's a fixable bug, it would probably be a smart idea to fix. > > Thaks, > Dan > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
