[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

[Steve Ebersole (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28305 ] 

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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira