This content has been marked as final.
Show 2 replies
-
1. Re: Executable file created by install4j can not be run
flavia.rainone Nov 11, 2008 6:50 AM (in response to cpsaop)Could you please try running aopc with this property enabled?
<sysproperty key="jboss.aop.instrumentor" value="org.jboss.aop.instrument.ClassicInstrumentor"/>
You must also run the application with this property set as above in order for this to work.
This will use an older instrumentation mode. If you stop from getting the VerifyError you mentioned, then we might have a bug in our generated advisor mode. if you still see the VerifyError, then the problem might be with install4j. It will recquire further investigation, though. -
2. Re: Executable file created by install4j can not be run
cpsaop Nov 12, 2008 11:03 PM (in response to cpsaop)Hi Flavia,
Many thanks for your reply. Actually, I have tried both of the instrumentors, ClassicInstrumentor(by the property you mentioned) and GeneratedAdvisorInstrumentor(by default), but VerifyError still occurs, although the exception message is different.
I am wondering, Will JBoss AOP community work on the integration issue with install4J? Currently, it's install4J launcher that doesn't support JBoss AOP weaving class. Hope for your response!!!
BR!
Hualin