Thanks Elco we are looking at the article right now. f(t)
PS: We have your early edition, it was great, it is great. Thank you. On Sun, Jun 29, 2008 at 3:50 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > I don't think it's Wicket's fault either, but someone could scan > Wicket's code for problems like described here: > http://blogs.sun.com/fkieviet/entry/classloader_leaks_the_dreaded_java > > Eelco > > On Fri, Jun 27, 2008 at 11:58 AM, Francisco Diaz Trepat - gmail > <[EMAIL PROTECTED]> wrote: > > Hi I send this mail to the Netbeans user list. And this is what some has > > responded. I don't think is the case, and I know this is a wicket list, > but > > could some-one developing wicket on netbeans 6.1 is dealing or has dealt > > with this issue? > > > > Thanks, > > f(t) > > > > ---------- Forwarded message ---------- > > From: Petr Hejl <[EMAIL PROTECTED]> > > Date: Fri, Jun 27, 2008 at 2:31 PM > > Subject: Re: [nbusers] WebApp Src/Html/css Updating ==> Redeploying / > > Refreshing Way > > To: [EMAIL PROTECTED] > > Cc: Petr Jiricka <[EMAIL PROTECTED]> > > > > > > Hi, > > this is usually bug (memory leak) in used framework. For example > hibernate > > is using PermGen space a lot and there were several issues (leaks) > related > > to this. It is usually related to dynamically created classes. > > P. > > > > > > Francisco Diaz Trepat - gmail wrote: > > > >> Hi, we are having the following problem, and believe it is the way we > work > >> with it. On developing mode the Apache Tomcat fails saying out of > memory. > >> > >> We are developing a Wicket app. > >> > >> Each change we do, we basically run the project again, or do a > right-click > >> ==> undeply and deploy > >> > >> Some times we touch a CSS or and HTML file, and have to touch a JAVA > file > >> just to reload it. > >> > >> After a few or better said, many, times of doing this (some touch, > re-run, > >> or undeploy-deploy) the Apache finally fails throwing an exception of > Out of > >> memory and something about perm objects. > >> > >> On Eclipse, a coworker is just Saving the CSS file to see the changes on > >> the Browser, he doesn't need to re-run or re-deploy. > >> > >> Can some one tell me what we are doing wrong? > >> > >> Thanks, > >> f(t) > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
