When implementing MOP you cannot intercept core Object methods (equals(), hashCode(), etc.)

Details

Type: Sub-task
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 1.0
Fix Version/s: None
Component/s: None
Labels:
None

Number of attachments :
0

Description

For some reason when attempting to intercept methods using the invokeMethod() routine there are a set of methods that are uninterceptable. The methods that I tested are:

equals()
hashCode()

I'm sure there are others. This seems like a hole in the whole MetaObjectProtocol, when intercepting methods I should be able to intercept all of them, not just some of them. Since this is being reworked I thought it would be a good time to file a bug.

Issue Links

depends upon

GROOVY-2503 MOP 2.0 design inflluencing issues

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Andres Almiray added a comment - 27/Nov/07 1:54 PM

Actually it looks like all methods belonging to Object will not be intercepted by invokeMethod, which may be a design constraint not to mess with the basic class, but definitely warrants another look when the MOP is revised.

Show

Andres Almiray added a comment - 27/Nov/07 1:54 PM Actually it looks like all methods belonging to Object will not be intercepted by invokeMethod, which may be a design constraint not to mess with the basic class, but definitely warrants another look when the MOP is revised.

Hide

Permalink

Guillaume Laforge added a comment - 17/Dec/07 4:10 PM

But EMC allows you to override everything, or even using GroovyInterceptable – the former being the advised way though.

Show

Guillaume Laforge added a comment - 17/Dec/07 4:10 PM But EMC allows you to override everything, or even using GroovyInterceptable – the former being the advised way though.

blackdrag blackdrag made changes - 17/Dec/07 5:15 PM