|Problem with AspectJ fast-matching [message #1270843]
||Thu, 13 March 2014 16:16
| Michael Beale
Registered: March 2014
trying to deploy an ear app which contains several war files and an EJB on glassfish 3, aspectj-1.7.4, spring-3.0.4, and get an exception of the type:
[#|2014-03-13T15:54:05.554+0000|INFO|oracle-glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=91;_ThreadName=admin-thread-pool-4848(2);|2014-03-13 15:54:05,552 [ad-pool-4848(2)] ERROR DispatcherServlet - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'applicationLoader' defined in ServletContext resource [/WEB-INF/XXXX.xml]: Cannot resolve reference to bean 'YYYY' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'YYYY':
Post-processing of the FactoryBean's object failed; nested exception is org.aspectj.weaver.reflect.ReflectionWorld$ReflectionWorldException: warning can't determine superclass of missing type com.sun.proxy.$Proxy298
I came across a similar question from about 3 years ago but it fizzled out.. Basically, it was unclear whether this was an AspectJ Weaving fast-matching bug or an app class-loading problem?? Would appreciate it if someone enlightens me.
Also, if I hack the aspectJweaver source so that the optimizedMatching is set to false, the ear deploys fine... However, despite trying several different ways (putting aop.xml in EAR/war/EJB.jar etc.) the weaver line:
doesn't seem to work???? (Neither does trying to supply this to glassfish as JVM-option???
Does this flag work,and if so, how ?????
Powered by FUDForum
. Page generated in 0.31747 seconds