Cool stuff. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tc-dev- > [EMAIL PROTECTED] On Behalf Of Geert Bevin > Sent: Friday, October 26, 2007 1:46 PM > To: [email protected] > Subject: [tc-dev] Small improvement to MergeTCToJavaClassAdapter > > Hi, > > just telling you all about a small change I did to > MergeTCToJavaClassAdapter. > > It will now not merge abstract methods of the TC classes into the > original classes. So for instance, any abstract method in > ConcurrentHashMapTC will not be merged into ConcurrentHashMap. > Before, this would always be the case, overriding any concrete > methods in ConcurrentHashMap. > > This is quite useful when you have a mixed instrumentation scenario, > like for ConcurrentHashMap where there are custom adaptors and a > sibling FooTC class with as much clean Java code as possible. This > allows the FooTC class to declare methods that are actually created > in the base Foo class through instrumentation in a custom adaptor, > for instance an original uninstrumented method implementation under a > new name. Since these methods are now declared in the FooTC class, > the clean Java code can use them and thus interact with the synthetic > byte-code generated methods. > > Beforehand, the only way that I could find to do this was to > introduce a bridge interface API. I think it's cleaner and more > productive to not have to do that anymore. > > Take care, > > Geert > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Music and words - http://gbevin.com > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev
_______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
