fyi...
http://weblogs.java.net/blog/ss141213/archive/2006/01/when_can_i_use.html

http://www.hibernate.org/374.html

I hope it's appropriate...

Thanks, but it would be better to submit this to JIRA.

Emmanuel is going to put some more time into getting HEM working right with Glassfish sometime soon.

If I find anything that's Hibernate's fault, I will. (Just like EJB-110.) The patch in the Wiki is a temporary workaround for a GlassFish issue that will eventually get fixed in some way or other -- and for the time being, Hibernate is more correct. I wouldn't want that patch in the Hibernate distribution...



I guess one of the main points is the classloader stuff (EJB-107). Is that work underway? how can I help best? (patch? stack trace?)

I actually have a very simple patch intended to the Glassfish application classloading code. But we need to clarify some stuffs on the spec to know whether this is HEM's or Glassfish's fault.
Currently this is nobody's fault ;-)

Look at http://fisheye5.cenqua.com/changelog/glassfish/?cs=MAIN:tware:20060120155455
Although ClassFileTransfrmer has been added now, it is still not used by container yet. But looks like things are coming closer.
It will be good to have these APIs issue sorted out, then the pluggability can be really tested. Class loading is going to be pose some issues and so will be dependency on open source libraries like Antlr etc.

The classloading needs to be clarified at the spec level to ensure portability
Antlr is not an issue with the latest release candidate