[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

[Andy Bailey (JIRA)]

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

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