[Hibernate-JIRA] Created: (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
11 p.m.
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
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
7:40 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on HHH-2222:
------------------------------------------
this is not just for Hibernate 3.2 it is for all previous versions of hibernate, so spring
made them self incompatible, right ?
workaround: use javassist as hibernates bytecode provider.
..and really bad that asm/cglib decided to become binary incompatible ;(
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
8:09 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on HHH-2222:
------------------------------------------
....this must only occur in some situations because i don't recall anyone noticing
this problem before ?
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
3:56 p.m.
New subject: [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...
]
Emmanuel Bernard commented on HHH-2222:
---------------------------------------
the vresion we use is not unknown, it is ASM 1.5.3
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
5:25 p.m.
New subject: [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...
]
Greg McGregor commented on HHH-2222:
------------------------------------
Thanks for the version feedback.
I was taking 3.2.0.ga and replacing the hibernate3.jar that Spring provided to bring the
latest bug fixes up to date when I noticed the problem. Since the JAR that ships from
Spring works fine (previous RC to 3.2) and your stuff works fine independently, I should
just stick with the Spring shipped release. The ASM versions each uses are much different
so I'm scratching my head. However, I would like to use 3.2.0ga so if I find
something useful, I'll comment back.
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
6:27 p.m.
New subject: [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...
]
Steve Ebersole commented on HHH-2222:
-------------------------------------
So which version of CGLIB is spring using then?
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
9:40 p.m.
New subject: [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...
]
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
10:36 a.m.
New subject: [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...
]
Alistair Bush commented on HHH-2222:
------------------------------------
Hi, I encountered this issue when trying to package hibernate-3.3.2 for Gentoo Linux
I have discovered that using cglib-2.1.3 and asm-1.5.3 works correctly.
This is based on a simple example that just generates 1 record in to the database (of only
1 table). Therefore as of yet I can not confirm whether these libraries will work in
general.
I should note that Gentoo is a source based linux distro and as such packages all third
party libraries separately, downloading and compiling the source that are available on
upstream websites, therefore the jars that I use may not be the exact versions used
within the hibernate release. We check API compatibility and SLOT ( mechanism for
installing different version of an package separately ) when necessary.
The following is the error trace that I receive when running my example using I am happy
to provide the example code if required. But will warn you that It is an adaption of the
first stages of the hibernate tutorial ( so not advanced at all )
Initial SessionFactory creation failed.java.lang.NoSuchMethodError:
org.objectweb.asm.ClassVisitor.visit(ILjava/lang/String;Ljava/lang/String;[Ljava/lang/String;Ljava/lang/String;)V
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.javacrm.core.HibernateUtil.<clinit>(HibernateUtil.java:33)
at org.javacrm.Main.createAndStoreTable(Main.java:45)
at org.javacrm.Main.main(Main.java:37)
Caused by: java.lang.NoSuchMethodError:
org.objectweb.asm.ClassVisitor.visit(ILjava/lang/String;Ljava/lang/String;[Ljava/lang/String;Ljava/lang/String;)V
at net.sf.cglib.core.ClassEmitter.begin_class(ClassEmitter.java:63)
at net.sf.cglib.core.KeyFactory$Generator.generateClass(KeyFactory.java:173)
at
net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:25)
at
net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:215)
at net.sf.cglib.core.KeyFactory$Generator.create(KeyFactory.java:145)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:117)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:108)
at net.sf.cglib.proxy.Enhancer.<clinit>(Enhancer.java:64)
at
org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:107)
at
org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.postInstantiate(CGLIBProxyFactory.java:43)
at
org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:162)
at
org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:135)
at org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTup
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
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
10:44 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on HHH-2222:
------------------------------------------
doesn't change the fact that it's asm is binary incompatible. How do they test
hibernate in spring2 testsuite ? must have the same issue.
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
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
8:24 p.m.
New subject: [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:
-----------------------------------
Alistair, I'm doing something very similar to you -- I'm integrating a source
build of hibernate, and I'm also using that version of hibernate in a spring source
build.
Spring uses the cglib-nodep artifact, which takes asm 1.5.3 and repackages it inside cglib
as net.sf.cglib.asm. Spring itself uses ASM 2.2.3 in a couple of places and uses it
unchanged from their stock distribution. This private version of asm is used only by cglib
and amounts to a private static dependency.
I've started work on a hibernate patch that uses the asm inside the cglib package, but
I haven't finished it yet (probably be done early of next week). Since Hibernate uses
1.5.3 ASM and cglib uses 1.5.3 ASM, it should work with only source changes.
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
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
11:08 p.m.
New subject: [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:
-----------------------------------
I've finished the patch work -- basically I changed instances of "import
org.objectweb.asm." to "import net.sf.cglib.asm" and used the
cglib-nodep.jar instead of cglib.jar. Once this is done, the build completes normally and
all unit tests that passed before the change pass after it.
After this, Hibernate and Spring can share a dependency on cglib-nodep without further
conflict.
I didn't bother to make a patch since the required changes are pretty obvious and I
don't think Hibernate really wants to change their dependencies. If that's an
incorrect assumption, I'd be happy to make a formal patch.
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
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
6:53 p.m.
New subject: [Hibernate-JIRA] Updated: (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 updated HHH-2222:
------------------------------
Attachment: HHH-2222.patch
Here's the patch I did for this. In addition, you'll need to replace
cglib-2.1.3.jar in your lib/ directory with cglib-nodep-2.1.3.
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
1:20 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on HHH-2222:
------------------------------------------
My question still stands:
"doesn't change the fact that it's asm that is binary incompatible. How do
they test hibernate in spring2 testsuite ? must have the same issue."
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
1:52 a.m.
New subject: [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
10:37 p.m.
New subject: [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...
]
Andy Bailey commented on HHH-2222:
----------------------------------
I just noticed that the asm faq has the solution to this problem
http://asm.objectweb.org/doc/faq.html
15 How to resolve conflicts between different ASM API versions available in a global
classpath or within the same ClassLoader?
Tools and frameworks that are using ASM for bytecode processing (e.g. Hibernate, CGLIB,
AspectWerkz) should repackage ASM code within their own name space. This can be automated
with Jar Jar Links tool. http://tonicsystems.com/products/jarjar/
-----------------
Jar Jar Links is a utility that makes it easy to repackage Java libraries and embed them
into your own distribution. This is useful for two reasons:
* You can easily ship a single jar file with no external dependencies.
* You can avoid problems where your library depends on a specific version of a
library, which may conflict with the dependencies of another library.
...
Jar Jar Links includes an Ant task (com.tonicsystems.jarjar.JarJarTask) that extends the
built-in Jar task. The normal zipfileset element is used to embed jar files. A new rule
element is added which uses wildcards patterns to rename the embedded class files.
Bytecode transformation (via ASM) is used to change references to the renamed classes, and
special handling is provided for moving resource files and transforming string literals.
Jar Jar Friendly Libraries: include ASM
... so it doesnt seem like any source code changes are needed !
Would it be possible to implement this in the hibernate build process so that it doesnt
conflict with other versions of asm that the user may need (its not just a
hibernate-spring problem)
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
1:11 a.m.
New subject: [Hibernate-JIRA] Assigned: (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...
]
Gail Badner reassigned HHH-2222:
--------------------------------
Assignee: Gail Badner
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
Assignee: Gail Badner
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
1:14 a.m.
New subject: [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...
]
Gail Badner commented on HHH-2222:
----------------------------------
I'll look into making the change so that hibernate can be used with Spring 2.x.
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
Assignee: Gail Badner
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
8:05 p.m.
New subject: [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...
]
Emmanuel Bernard commented on HHH-2222:
---------------------------------------
I might be wrong but I think we tried that and bytecode enhanced classes had issues, maybe
it worths a second look
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
Assignee: Gail Badner
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
10:31 p.m.
New subject: [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...
]
Steve Ebersole commented on HHH-2222:
-------------------------------------
I am absolutely against repackaging within Hibernate. And in fact repackaging within
cglib is at best a band-aid with one side of its stickiness worn off; as soon as you have
two versions of cglib doing this repackaging you have the same issue.
Generally speaking, as a container it is Spring's responsibility to isolate its
implementation details from its users. This is *exactly* the reason that app servers do
this re-packaging of libraries all the time.
As for Hibernate users, there is a trivial work around: use javassist for the bytecode
provider.
Long term, as soon as cglib has a release using asm 2.x (it looks like cvs currently has
asm 2.2.1) we will move to that.
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
Assignee: Gail Badner
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
10:42 p.m.
New subject: [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:
-----------------------------------
Steve, I want to understand where you're coming from. Are you saying that it's
Spring's responsibility to repackage their libraries, since they're a framework,
while Hibernate doesn't have to since it's not? I think I understand the
philosophical point, but as a practical matter, this would make life a lot easier for
Spring users. What am I missing?
Also, what if using javassist isn't an option for a Hibernate user? (Company policy of
Officially Approved open source, license problems, etc.)
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
Assignee: Gail Badner
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
11:54 p.m.
New subject: [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...
]
Steve Ebersole commented on HHH-2222:
-------------------------------------
> Are you saying that it's Spring's responsibility to
repackage their libraries
Yes, in so far as those implementation details leak out to
users and effect them. In fact, in contrast, Hibernate goes out of its way to not expose
the underlying bytecode provider library to user, instead using a contract or facade.
> since they're a framework, while Hibernate doesn't have
to since it's not
Spring is *not* a framework. They have hood-winked you ;)
They are a container, just like any app server. Of course to admit to that takes away
their edge.
> Also, what if using javassist isn't an option for a Hibernate
user? (Company policy of Officially Approved open source, license problems, etc.)
Well, I'd say you might want to reconsider that policy. And licensing is not a
valid argument since javassist is distributed under LGPL just as Hibernate; you can't
take issue over the LGPL in relation to one library, but not another...
We will upgrade to CGLB 2.2 as soon as it is ready to go. CGLIB 2.2 is set to use ASM
2.2.x (I think 2.2.1 currently) which then should alleviate this condition. Gail is
investigating this to make sure we are correct in this understanding.
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
Assignee: Gail Badner
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
midnight
New subject: [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:
-----------------------------------
I see where you're coming from now. Thanks for talking slowly and using big words for
me. :)
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
Assignee: Gail Badner
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
12:25 a.m.
New subject: [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...
]
Steve Ebersole commented on HHH-2222:
-------------------------------------
I also "walk softly and carry a big stick" ;)
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
Assignee: Gail Badner
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
12:27 a.m.
New subject: [Hibernate-JIRA] Closed: (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...
]
Steve Ebersole closed HHH-2222.
-------------------------------
Resolution: Rejected
HHH-2875
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
Assignee: Gail Badner
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
1:50 p.m.
New subject: [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...
]
Travis commented on HHH-2222:
-----------------------------
Workaround: http://forum.hibernate.org/viewtopic.php?p=2373390#2373390
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
Assignee: Gail Badner
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
5:37 p.m.
New subject: [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...
]
Andy Bailey commented on HHH-2222:
----------------------------------
Depending on the options used in spring the above workaround may or may not work, if you
use the ClassPathScanner or an option that depends on using the ClassPath scanner the
solution doesnt work. (see http://jira.springframework.org/browse/SPR-3856 for more
details)
The Spring Team fixed the problem in Spring 2.5 by repackaging ASM, so the real solution
is to upgrade to spring 2.5
Andy Bailey
http://www.hazlorealidad.com
Quote from Juergen Hoeller (from the above jira report)
We do repackage ASM for Spring 2.5 now (as part of spring.jar and spring-core.jar),
avoiding conflicts with other ASM versions as well as making it easier to use Spring's
component scanning feature (no need for adding any asm-* jars for those purposes
anymore).
This required a revision of Spring's "core.type" package, using ASM
internally now, with no ASM artifacts exposed publically - meaning that other packages
(other Spring framework packages as well as third-party packages) can use
"core.type" without being tied to the original or repackaged ASM location.
Juergen
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
Assignee: Gail Badner
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
6008
days inactive
6442
days old
hibernate-issues@lists.jboss.org
25 comments
9 participants
participants (9)
-
Alistair Bush (JIRA) -
Andy Bailey (JIRA)
-
Ben Speakmon (JIRA)
-
Emmanuel Bernard (JIRA)
-
Gail Badner (JIRA)
-
Greg McGregor (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Steve Ebersole (JIRA)
-
Travis (JIRA)