> > Hi Jens, > > Ya, we're experiencing the same problem. The Spring context fails to load. > I also noticed that it doesn't happen prior to 1.6.7. I don't know the > exact reason why but I suspect it has to do with the Fast Matching turned > on by default in 1.6.7. Unfortunately my attempts to disable it within an > OSGi environment have failed. You might have better luck if you're working > in a standard environment and configure aop.xml. > > Thanks, > Dustin Schultz >
Hi Dustin, we also use OSGi. Therefore simply using an aop.xml was not very promising to us. We tried to isolate this nasty thing and finally found a workaround for our problem. May this helps in your case, too. While debugging we saw that the error occurs when proxies for exported osgi services (<blueprint:service ...> are handled. These are instances of OsgiServiceProxyFactoryBean. So we added a package import for this package to our manifest: org.eclipse.gemini.blueprint.service.exporter.support;version="1.0.2.RELEASE", And after subsequent debugging we added some more import statements: org.springframework.aop;version="3.2.0.RELEASE", org.springframework.aop.aspectj;version="3.2.0.RELEASE", org.springframework.aop.framework;version="3.2.0.RELEASE", org.springframework.aop.interceptor;version="3.2.0.RELEASE", Now everything works like a charm. I am not really sure wether this is the right solution or just a hacky workaround for the real problem. If it is the solution at least better diagnosing messages would be needed. Any opinions about our findings? Cheers, Jens _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
