Your questions are not specific to JBoss, but are specific to the J2EE spec. I suggest you find yourself a good reference. I reccommend "Java Server Programming J2EE 1.3 Edition" Wrox Press
> I've tried adding "Class-Path: lib/common.jar"-like
> entries to MANIFEST.MF in the ear, web and ejb
> modules without any luck.
The Class-Path: has worked for me (one utility jar with a bean that is used both from the webapp and an EJB.
You should not need to have it in the .ear MANIFEST.MF, only in the webapps and ejb.
I think there needs to be a newline after the Class-Path: line (or two :-) ). Have you checked that the manifest file is put correctly in the jar? (Inside the META-INF directory). You must give it separately to the jar command when creating the webapp/ejb (flag -m maybe?).
My goodness, the -m option in jar. Being pretty new to the J2EE game, I didn't realize that whatever MANIFEST.MF I included in the files list for jar wouldn't neccessarily be kept if I didn't specify it with -m.
Why is the most frustration always causes by the dumbest problem?