[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2222) SpringFramework 2.0 uses ASM.JAR versions 2.2.2. This is incompatible with Hibernate 3.2 as it uses and "unknown" previous version of ASM.JAR
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222?page=c...
]
Ben Speakmon commented on HHH-2222:
-----------------------------------
Spring's tests don't exercise any part of Hibernate that uses cglib, and cglib is
where the ASM incompatibility is. They test against a precompiled Hibernate jar and
don't import any of the Hibernate classes that import org.objectweb.asm directly;
i.e., classes in the patch (org/hibernate/bytecode/cglib/CglibClassTransformer.java,
org/hibernate/bytecode/cglib/BytecodeProviderImpl.java,
org/hibernate/tool/instrument/cglib/InstrumentTask.java). That's why it's not a
problem for them. If they had any test that did in fact touch those classes, it would
break (and if I change a Spring test to do that, it fails to compile).
As far as I can tell, there is no difference between the hibernate3.jar included with
Spring and the jar distributed from hibernate.org.
SpringFramework 2.0 uses ASM.JAR versions 2.2.2. This is
incompatible with Hibernate 3.2 as it uses and "unknown" previous version of
ASM.JAR
----------------------------------------------------------------------------------------------------------------------------------------------
Key: HHH-2222
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222
Project: Hibernate3
Issue Type: Improvement
Affects Versions: 3.2.0.ga
Environment: Hibernate 3.2.0ga
Reporter: Greg McGregor
Attachments: HHH-2222.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
SpringFramework 2.0 uses ASM.JAR from ObjectWeb version 2.2.2. However, Hibernate
3.2.0ga utilizes an "unknown" previous version of the ASM.JAR. The issue is
that the method signatures and classes have changed between the two versions. Therefore,
Hibernate 3.2.0ga won't run with the new ASM.JAR and Spring 2.0 won't run with the
previous ASM.JAR. Mushing the two JARs together in an attempt to get something going
results in a NoSuchMethodError (which would make sense).
Although this isn't a direct Hibernate3 bug, it does preclude stable use with Spring
2.0/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira