The error given by the binding compiler is a JVM verifier error. I found that the issue can be fixed by setting the JVM option "-XX:-UseSplitVerifier". According to [1], this forces to use the old JDK 1.6 verifier.
Thanks, ~Isuru [1] http://stackoverflow.com/questions/7970622/java-7-jvm-verifyerror-in-eclipse/7970870#7970870 On Thu, Apr 19, 2012 at 12:18 PM, Isuru Suriarachchi <[email protected]> wrote: > AS Jibx sample fails on JDK 1.7 and I had a look at the failing step. It > fails when running the binding compiler. According to [1], binding compiler > does the byte code enhancements on the compiled java classes and that is > how Jibx works. But even if I remove the binding compiler from the ant > build by commenting out the following target, the sample works fine. > > <!-- Run JiBX binding compiler --> > <!--target name="jibx-binding-compiler" depends="compile-all"> > <bind verbose="true" load="true" binding="conf/jibx_unwrapped.xml"> > <classpath> > <pathelement path="${classes}"/> > <path refid="axis2.class.path"/> > </classpath> > </bind> > </target--> > > Then I just checked the Axis2 jibx samples as well. But it also doesn't > have this binding compiler step. Does anyone has an idea about how it works > without this step and whether we can get rid of this step? > > Thanks, > ~Isuru > > [1] http://jibx.sourceforge.net/index.html > > -- > Isuru Suriarachchi > Technical Lead > WSO2 Inc. http://wso2.com > email : [email protected] > blog : http://isurues.wordpress.com/ > > lean . enterprise . middleware > > -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : [email protected] blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
