Thanks Richard for filing this bug which is so clear on what is the
cause and what is the workarounds as following:
We have existing current Hibernate applications that were written for GlassFish 2.1
But now they don't work in GlassFish 2.1.1
The core reason is 2.1.1 has a new library that clashes with Hibernate.
There is nothing to fix, I would just like this documented please.
This will also effect our Spring brothers.
Known workarounds :
1) in your sun-web.xml set <class-loader delegate="false"/>
2) manually delete the "asm-3.1.jar" file in the <glassfish-install-dir>/lib/
directory and copy an old version of "asm-<v_num>.jar" in its place.
Judy :-)
Richard Kolb wrote:
> Hello Cats
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=12812
>
> regards
> Richard
>
>
> On 26 July 2010 13:32, Richard Kolb <rjdkolb_at_gmail.com
> <mailto:rjdkolb_at_gmail.com>> wrote:
>
> Hello Cats
>
> Hope you are not all having a cat nap since FishCAT time is not
> currently happeing.
>
> Strange issue I had with my old Hibernate application on GF 2.1.1
>
> It seems 2.1.1 includes asm-3.1.jar, while 2.1 did not.
>
> asm 3.1 clashes with Hibenate.
>
> http://tai-dev.blog.co.uk/2010/01/21/nosuchmethoderror-org-objectweb-asm-classwriter-when-deploying-your-app-to-a-new-instance-of-glassfish-v2-1-1-it-looks-like-the-upgraded-fins-are-7849068/
>
>
> Deleting the JAR can't be the answer right ?
>
> Any suggestions ?
>
> regards
> Richard.
>
>