On Sat, Oct 31, 2009 at 4:06 PM, Stuart McCulloch <[email protected]> wrote:
> FYI if you look at the concrete class it will probably have two methods > as well - the original method and another generated by the compiler to > fudge the return type to match the interface. > > Using reflection "method.isSynthetic()" will return true for the compiler > generated method. When intercepting I usually ignore any synthetics > as they're just layers/adapters on top of the real method. Thanks. Very interesting. Have seen the method before, but never really checked what it was for. Well, then I think we might have a general issue in our method resolution system, as if synthetic method is 'ignored', we don't find the correct one in Qi4j. IOW, we don't have our own method matching, which seems to be needed. Got any tips on how to go about it in a safe manner? Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
