geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <>
Subject Re: net.sf.cglib.core.CodeGenerationException: what does usually mean
Date Tue, 23 Nov 2004 18:48:32 GMT
	We might as well poll to see if anyone's using it, but it just
seems dangerous to keep around in principle.  I'd rather make people
implement the interface and have some methods throw an
UnsupportedOperationException instead of getting some kind of "method
doesn't exist" error out of CGlib...  It's not clear in that case that 
it's the callee's fault not the caller (or builder's) fault.


On Tue, 23 Nov 2004, Dain Sundstrom wrote:
> I consider it a feature, but that doesn't mean we should keep it.  It 
> is there so you can adapt older components to gbeans easier.  For 
> example, if you can create an interface for several components and not 
> call some of the methods you *know* are not implemented.  The obvious 
> question is how do you *know*, in 77 they have lots of methods like is 
> StatisticsProvider.  If the bean is a statics provider then you know 
> that it has a getStatistics method.  Alternatively, your code could use 
> the GBeanInfo to figure out what methods are useful.
> Anyway, I don't sure anyone is using this feature, so if everyone finds 
> it is more confusing then, then I vote +1 to remove it.
> -dain

View raw message