Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.0
-
Fix Version/s: 3.0
-
Component/s: None
-
Labels:None
-
Number of attachments :
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
| This issue depends upon: | ||||
| GROOVY-2503 | MOP 2.0 design inflluencing issues |
|
|
|
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.