It looks like Java 1.7 made non-backward compatible changes to the
bytecode verifier, and now requires some sort of new instruction
structure. I haven't found where this is spelled out in the Java 1.7
documentation, but Snoracle doesn't seem especially forthcoming about
the changes they're making to "their" language.
In other cases I found by searching online people were able to avoid the
problem by using the jvm option -XX:-UseSplitVerifier. You might try
that to see if it works as an interim solution. I'll download Snoracle's
1.7 to duplicate the problem myself and see if I can find out why it occurs.
- Dennis
Dennis M. Sosnoski
Java SOA and Web Services Consulting <http://www.sosnoski.com/consult.html>
Axis2/CXF/Metro SOA and Web Services Training
<http://www.sosnoski.com/training.html>
Web Services Jump-Start <http://www.sosnoski.com/jumpstart.html>
On 11/16/2011 07:53 AM, Don Corley wrote:
Adam,
I get the same error when I run the current JiBX test suite under
jdk1.7. This bug has been entered at:
http://jira.codehaus.org/browse/JIBX-465
Thanks for reporting this.
Don
----------------------------------------------------------------------
Message: 1
Date: Mon, 31 Oct 2011 15:00:24 -0500
From: Adam Weigold <aweig...@vitalimages.com
<mailto:aweig...@vitalimages.com>>
Subject: [jibx-users] Java 7 and JiBX 1.2.2
To: "jibx-users@lists.sourceforge.net
<mailto:jibx-users@lists.sourceforge.net>"
<jibx-users@lists.sourceforge.net
<mailto:jibx-users@lists.sourceforge.net>>
Cc: Grant Cermak <gcer...@vitalimages.com
<mailto:gcer...@vitalimages.com>>
Message-ID:
<216a50e5c959a144b5c12b10ff23334b0112b3b7a...@srv-exchmbx.vitalimages.com
<mailto:216a50e5c959a144b5c12b10ff23334b0112b3b7a...@srv-exchmbx.vitalimages.com>>
Content-Type: text/plain; charset="utf-8"
Hello,
We are working to migrate to Java 7 (1.7.0_01) and are having
incorrect bindings when using the JiBX maven plugin (1.2.2).
Is Java 7 supported by JiBX 1.2.2 or are we likely 'doing
something wrong'?
I have run compile jibx:bind with both verify and load options set
to true, neither fail. Running with verbose doesn't yield
anything abnormal looking. However after trying to perform
unmarshalling, errors like this appear:
testVitalConfig2(com.vitalimages.common.server.config.VitalConfigTest)
Time elapsed: 0.001 sec <<< ERROR!
java.lang.VerifyError: Expecting a stackmap frame at branch target
12 in method
com.vitalimages.common.server.config.VitalConfig.JiBX_VitalConfig_newinstance_1_0(Lcom/vitalimages/common/server/config/VitalConfig;Lorg/jibx/runtime/impl/UnmarshallingContext;)Lcom/vitalimages/common/server/config/VitalConfig;
Thanks,
--
______________________________________________________________________________________________
[cid:1320090316.3232.4.camel@ubuntu-aweigold1] Adam J. Weigold |
Software Engineer
5850 Opus Parkway, Suite 300 l Minnetonka, MN 55343
952.487.9835 <tel:952.487.9835> l 866.433.4624 <tel:866.433.4624>
l www.vitalimages.com
<http://www.vitalimages.com><http://www.vitalimages.com/>
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
