|
From: Rob H. <ro...@ca...> - 2004-06-25 07:59:47
|
I'll check that out and see if it needs revising. I think as long as the advisors are the same then the same proxy class can be used. I will look into this some more today. Rob Chris Nokleberg writes: > Norris, Tyson wrote: >> (Using the CVS version 1.8 Cglib2ApoProxy) I get everything to work fine >> with the test case I mentioned below even when both proxies are advised, >> unless I remove the equals() method from TestBean. > [snip] >> So, my question is - why should this affect whether CGLIB can cache the >> generated class? I'm back to not understanding if the problem is in >> CGLIB, or Cglib2AopProxy. (or, maybe I'm missing some understanding, and >> the equals method on my beans truly is required...) > > The new ProxyCallbackFilter class still uses AopProxyUtils.equalsInProxy in > its equals method. equalsInProxy uses equality of the AdvisedSupport > TargetSource. Depending on the implementation of TargetSource being used, I > think this means it *is* possible for your target bean's equals method to > affect CGLIB caching behavior. I'm not qualified to say whether this is > desirable or not. > > Chris > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |