Hi Andy,

Thanks for your response. I'll see if I can work on a test case this week.

Thanks,
Dustin Schultz

From: Andy Clement <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Monday, January 7, 2013 2:51 PM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [aspectj-users] ReflectionWorld.resolve(String) and Dynamic Proxy 
Classes

Hi Dustin,

I think it is probably just the case that there is no special handling for 
dynamic proxies in there. I would be OK with making a change to recognize the 
situation sooner and circumvent the unhelpful message.  I'd need a testcase 
before I could do the work myself but if you wanted to come up with a patch, 
I'd take that (I'd just have to confirm all the Spring test suites still pass 
with it in place, which I can do, I don't have a comprehensive AspectJ test 
suite for reflection world).

cheers,
Andy


On 4 January 2013 10:31, Dustin Schultz 
<[email protected]<mailto:[email protected]>> wrote:
Also, here is the relevant method which calls resolve() is 
PointcutExpressionImpl:

public boolean couldMatchJoinPointsInType(Class aClass) {
ResolvedType matchType = world.resolve(aClass.getName());
…
}

Thanks,
Dustin Schultz
From: Dustin Schultz <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Friday, January 4, 2013 11:23 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: [aspectj-users] ReflectionWorld.resolve(String) and Dynamic Proxy 
Classes

Hi,

I was going to file a bug about this but wanted to ask first before doing so:

Is there any particular reason that ReflectionWorld.resolve(String) tries to 
resolve dynamic proxy classes by name? Class.getName() for dynamic proxies 
always returns $Proxy# and ReflectionWorld can never resolve them which always 
results in a cantFindType error.

Granted, I can turn down cantFindType to warning, the default in 
Xlint.properties is error. We're currently experiencing this when Spring goes 
looking for beans to advise. It runs into a bean that is already proxied (an 
OSGi service reference) and then blows up.

Thanks,
Dustin Schultz

_______________________________________________
aspectj-users mailing list
[email protected]<mailto:[email protected]>
https://dev.eclipse.org/mailman/listinfo/aspectj-users


_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Reply via email to