Hello,

I have read the "Using Hibernate with JBoss" document and included the recommended .jar files (and put them in the manifest file), but I still get

WARN [org.jboss.ejb.EJBDeployer] Verify failed; continuing
java.lang.NoClassDefFoundError: net/sf/hibernate/HibernateException

when I try to deploy the ejb-jar using Hibernate contained in that .ear.

Anyone have a working set of jar:s to include (or any other hints)? I understood that the NoClassDefFoundError could come from almost any dependent .jar along the line

I use WebLogic instead of JBoss, but this is a pretty common issue. The way it works for me in WL (and it should also work in JBoss) is as follows:
1) generate my ejb-jar files with Class-Path entries in each ejb-jar manifest file with each of the jar files listed which this ejb grouping needs;
2) bundle the ear file with all the jar files referenced in the ejb-jar manifests loaded into the root of the ear file.

This also works for classes, resources, etc.

I did run into problems with the manifest Class-Path getting longer than one line. The jar spec has some crazy requirements regarding line length for manifest file entries. I cannot remember all the details, but the jist was a line neede to wrap at exactly 72 characters eith the proceeding line indented 1 space. The problems I ran into were (using Ant to generate these) with jar file names wrapping in the middle of the name.

The jar spec allows multiple Class-Path entries, so you should be able to avoid this by breaking up each jar into seperate entries, but the weblogic ejbc utility does not respect that part of the spec and only uses the last entry. If thats not a limit in JBoss, that thats all you need.

Tried splitting the Class-Path into multiple entries (it did seems to break in a bad place) in both the ear and ejb-jar manifest, and I still have the jars in the root of the .ear but no luck. The document mentions copying the jar:s to the server classpath but it shouldn't be neccessary. Or?

Steve,
It would be good to get a contrib page on setting this up for Weblogic as you mention issues for which it would be great to have more complete example documentation.

Thats a good idea. My issues were specific to WL 6.1. We are in the process of moving to WL 8.1, so I'll soon have some insight into that setup also...

Well I'll be damned, looks like the "Or?"-part should be applied. Copying the jars:s to the server lib helped! Looks like you should follow the instructions in the help document instead of just reading it ;-)

Now I'll go to the JBoss forums and bug them why this is required because I don't think this is normal behaviour...

My JBoss setup includes the libs in the deploy directory. I have been meaning to stup the EAR as libs located in the EAR should work correctly. It is also a better solution. Everytime I upgrade its is pain. I will try it out and see how we go.

Yes, I would also be interested in knowing how to make the EAR as stand-alone as possible, let me know how your experiment turns out. Could it be something with the order the classloading is done for the components?

Each version of JBoss has tended to have changes to the classloader. This is why I have left a working solution (although not ideal) as I generally have other things to do. Now I do understand that v3.2.x is better in this area so it worth trying it out. I will see how I go and update the wiki. The JBoss info is a little mixed up and should be better organised.