Or better yet (as my test manager now won't allow a Spring upgrade), any thoughts on a workaround or fix still using 2.1?
Type: Posts; User: brad103; Keyword(s):
Or better yet (as my test manager now won't allow a Spring upgrade), any thoughts on a workaround or fix still using 2.1?
Hi Marten
I've figured it out. I am running Spring 2.1. I downloaded 2.5 and got the same output as you (although mine shows Object as the param type for the generic class, but that's not major)....
Thanks Marten
I've checked and re-checked everything. Here is actual code that illustrates the problem:
pkg/config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<beans...
Hi Marten
You're right, I've got a typo is in the example I posted here. The pointcut should read:
Around('execute(public * pkg.MyIface.do(..))')
So the problem still stands. Any more ideas?...
Do you mean when you had an include line for mailingCommand in <aop:aspectj-autoproxy>? My understanding is that the only beans you should define in here are those that define aspects (use @Aspect...
Looks to me like it's trying to double-proxy a class. Proxies are final, which is why Spring can't proxy the $Proxy6 class. I haven't used the ProxyFactoryBean before myself, but you might want to...
I have existing pointcuts working fine advising various methods in a class. I tried adding just one more, identically set up, and it wouldn't work. After much debugging, I've discovered that if a...
That's it! Exactly right, thanks a lot.
:)
The reason this wasn't obvious to me is that I'm utilising the class statically and just using Spring to initialise the class, then ignoring Spring's...
Thanks Andrei
Basic test class:
import static org.junit.Assert.assertTrue;
import org.junit.Test;
import org.springframework.context.support.AbstractApplicationContext;
import...
I have a Spring AOP autoproxying that works fine until the introduction of my new bean. The purpose of this new bean is for Properties handling. Its bean definition is:
<!-- Wrap policy...