Re: [Springframework-developer] Not leveraging the CGLIB cache

[Colin S. <col...@ex...>]

James,

This is a bug which is fixed in CVS head (post 1.0.2). 1.0.2 and earlier 
were indeed not caching classes, and I personally ran out of 'Perm' 
space in an app because of this, but the new code seems to work fine. 
Make sure you upgrade to the cglib-1.0.2.jar that is in CVS as well. It 
actually represents CGLIB head, which the new code depends on.


James Cook wrote:

>Rod,
>
>Do you remember this issue? Has this one been addressed yet?
>
>http://article.gmane.org/gmane.comp.java.springframework.user/1502
>
>From: Chris Nokleberg <chris <at> sixlegs.com>
>Subject: Re: CGLIB proxies are not assignable
>Newsgroups: gmane.comp.java.springframework.user
>Date: Sun, 11 Apr 2004 17:15:30 +0000
>
>Rod Johnson <rod.johnson <at> interface21.com> writes:
>  
>
>>This is the behaviour I would expect. As you say, maybe we should 
>>add it to the docs. All proxies _are_ instances of the class to be
>>proxied.
>>    
>>
>
>I actually think this is a bug. If the name of the class is changing 
>it means that caching of generated classes is not working correctly
>--it is probably generating a new class per proxy. This will obviously 
>slow down proxy creation tremendously and eventually cause
>OutOfMemoryExceptions. The typical culprit is when you use a 
>custom CallbackFilter that does not implement equals/hashCode. I
>don't have time right now but I'll take a look soon.
>
>Happy Easter
>Chris
>  
>