On 7/28/06, James Carman <[EMAIL PROTECTED]> wrote:
The memory leak issue is well-known and somewhat well-documented: http://wiki.apache.org/jakarta-commons/Logging/UndeployMemoryLeak
Yes and this is more an underlying class loader issue rather than specific to commons logging. I agree with James, it would be better to handle the release of resources in a WebRequestServiceFilter otherwise, there would still be space for some classloading issues there, no matter what framework is used. -- Henri Dupre Actualis Center
