Caused by: java.lang.IllegalArgumentException: warning no match for this type name: com.qualitype.genetics.ref.io.ReferenceDataManager [Xlint:invalidAbsoluteTypeName]
at org.aspectj.weaver.tools.PointcutParser.parsePointcutExpression(PointcutParser.java:301)
at org.springframework.aop.aspectj.AspectJExpressionPointcut.buildPointcutExpression(AspectJExpressionPointcut.java:207)
at org.springframework.aop.aspectj.AspectJExpressionPointcut.getFallbackPointcutExpression(AspectJExpressionPointcut.java:358)
at org.springframework.aop.aspectj.AspectJExpressionPointcut.matches(AspectJExpressionPointcut.java:255)
at org.springframework.aop.support.AopUtils.canApply(AopUtils.java:209)
at org.springframework.aop.support.AopUtils.canApply(AopUtils.java:263)
at org.springframework.aop.support.AopUtils.findAdvisorsThatCanApply(AopUtils.java:295)
at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.findAdvisorsThatCanApply(AbstractAdvisorAutoProxyCreator.java:117)
at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.findEligibleAdvisors(AbstractAdvisorAutoProxyCreator.java:87)
at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.getAdvicesAndAdvisorsForBean(AbstractAdvisorAutoProxyCreator.java:68)
at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.wrapIfNecessary(AbstractAutoProxyCreator.java:359)
at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.postProcessAfterInitialization(AbstractAutoProxyCreator.java:322)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:407)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1461)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
... 39 more

Before using pointcuts in the blueprint configuration I tried the @Transactional annotation and it was working fine. Now using pointcuts I have this classloading trouble. I'm wondering if it is possible to use pointcuts in the blueprint configuration file?]]>Sebastian Lorenz2012-11-07T14:54:10-00:00Re: Pointcuts in blueprint xml configuration causes classloading issuehttps://www.eclipse.org/forums/index.php/mv/msg/430564/975093/#msg_975093
Virgo FAQ if you want to avoid hacking 3rd party bundle manifests). There is also some historic information on this subject here, but my feeling is that you are trail-blazing... ]]>Glyn Normington2012-11-07T15:42:47-00:00Re: Pointcuts in blueprint xml configuration causes classloading issuehttps://www.eclipse.org/forums/index.php/mv/msg/430564/976231/#msg_976231
Well, my intention was to avoid any hard-coded spring dependencies, but for now I switched back to using the @Transactional annotation.

Btw. The OSGi Early Draft 2012.10 describes how to use transactions in osgi. Is using @Transactional "supported" or should I use bean-managed transactions?]]>Sebastian Lorenz2012-11-08T12:18:43-00:00Re: Pointcuts in blueprint xml configuration causes classloading issuehttps://www.eclipse.org/forums/index.php/mv/msg/430564/977779/#msg_977779
Glyn Normington2012-11-09T15:16:42-00:00