[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222?page=c...
]
Greg McGregor commented on HHH-2222:
------------------------------------
Thank you for the replies. I have been looking into this further and although the Jars
are different, using the JAR from Spring works with Hibernate 3.2.0rc4 (?). It looks like
our encrypted custom class loader worked fine in Spring 1.x but not with 2. Initially it
pointed at this issue. I believe this is just a change in Spring 2 that we have to
account for. Thank you for the feedback.
I think this link is realitve to my issue but not sure yet:
http://opensource.atlassian.com/projects/spring/browse/SPR-2156
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
Type: Improvement
Versions: 3.2.0.ga
Environment: Hibernate 3.2.0ga
Reporter: Greg McGregor
Original Estimate: 0 minutes
Remaining: 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