aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Another weaving problem?
Date Fri, 03 Jun 2011 15:10:57 GMT
I'm tired of being in the middle of this.  Please discuss this on the owb dev list or in comments

The problem in owb is that although the actual proxy building code has no problems with the
final synthetic methods, there's an excessively naive check for proxyability that just looks
at all declared methods and checks they aren't final.  Based on this example, I think there
may be a  lot of existing code with similar errors that works fine in most situations but
will not work with aries.

I'll commit a fix to owb too so everyone is unhappy.  if you folks can convince the owb folks
that the methods should be final I'll put the final back in aries.

david jencks
On Jun 3, 2011, at 7:38 AM, Holly Cummins wrote:

> Richard Ellis wrote:
>> I'm not going to comment on whether final methods perform better or not, 
>> but the other reason the methods are marked final is to stop people 
>> overriding them when they shouldn't. There is no reason for another 
> proxy 
>> (or anything outside of Aries) to override the methods added by the 
> Aries 
>> proxy. The methods are (and should) only be called by the Aries code 
> when 
>> it needs to perform proxy actions.
> [...]
> That's a really good point Rich, which I should have added in my comment. 
> We should mark methods final for semantic reasons (like "People have no 
> business overriding this"), rather than performance reasons. That has the 
> added bonus that it's clear when a method is marked final what the 
> underlying intention is. Well, clearer, at least!
> Holly
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number 
> 741598. 
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

View raw message