[SPRNET-1314] AttributeMatchMethodPointcut should support explicitly implemented interfaces Created: 25/Feb/10  Updated: 09/Dec/10  Resolved: 08/Apr/10

Status: Resolved
Project: Spring.NET
Component/s: Spring-NET-AOP
Affects Version/s: 1.3.0 RC1, 1.3.0
Fix Version/s: 1.3.1

Type: Bug Priority: Minor
Reporter: Mike P. Mikhailov Assignee: Bruno Baia
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WinXP, Vista, MSVS2008, FW3.5


Attachments: Text File AttributeMatchMethodPointcut.cs     Text File AttributeMatchMethodPointcut.cs     Text File AttributeMatchMethodPointcutTests.cs     Text File AttributeMatchMethodPointcutTests.cs    

 Description   

When matching the methods AMMP does not take into account that the methods may be implemented explicitly.
Target (matching) method name will contain the original interface name in front of the method name.
So additional check is required.

I've attached the modified version of the AMMP alone with the modified test case for it.



 Comments   
Comment by Mike P. Mikhailov [ 25/Feb/10 ]

Sorry, the files atteched in the original issue contains no fixes. The correct files at the position 3 and 4.

Comment by Mike P. Mikhailov [ 25/Feb/10 ]

Fixed for incorrect original files

Comment by Bruno Baia [ 08/Apr/10 ]

Thanks for the patch Mike !

I've made some changes to take into account methods from multiple interfaces with the same name and parameters.
Check the source tab to see changes in SVN.

Generated at Wed Jul 15 09:58:13 UTC 2020 using Jira 8.5.4#805004-sha1:0444eab799707f9ad7b248d69f858774aadfd250.