Re: [Springframework-developer] Re: Proxying target classes

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

Les A. Hazlewood wrote:

>>Colin Sampaleanu wrote:
>>    
>>
>>>The class is not final, and there are no final methods. And I was wrong,
>>>it actually already implemented one interface, InitializingBean.
>>>      
>>>
>>I sent a reply before but it didn't show up. I'm pretty sure this is a bug
>>that was fixed recently in CGLIB CVS. If you could try with a newer jar
>>file I would appreciate it, otherwise let me know how to reproduce the
>>problem.
>>    
>>
>
>As I've missed the beginning of this thread, I apologize if what I'm about to
>ask was the exact same question about Proxying via CGLIB ;)  If not, it still
>is related.
>
>We recently came across an issue that might prevent us from using Spring
>(because of CGLIB dependencies) in client-tier swing/webstart/applet
>deployments.
>  
>
Just to clarify; if you are ok with proxying only by interfaces (the 
default for Spring, controlled by the 'proxyTargetClass' param on the 
proxy factory bean classes), then Spring actually does not have any 
cglib dependencies; it will use a standard J2SE proxy.

Now if you do set that flag to true, then it will use cglib and you will 
have the issues you mention in your environment...

Regards,
Colin