The memory leak issue is well-known and somewhat well-documented: http://wiki.apache.org/jakarta-commons/Logging/UndeployMemoryLeak
-----Original Message----- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: Friday, July 28, 2006 4:22 AM To: Tapestry development Subject: Re: T5: getting away from commons-logging On 7/28/06, Henri Dupre <[EMAIL PROTECTED]> wrote: > On 7/27/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > > > A pretty common complaint is that commons-logging is a problem. It > > does some wierd and awkward class loading things that ultimately > > result in memory leaks. > > > I think they solved this issue in their latest version. And given how > used this project is, I'm sure they will fix the remaining issues. > Btw, I have not seen any memory leaks with commons-logging that far. Just do a quick search over googlandia to find out a lot of nesty things around it. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
