EJBs don't completely connect with
J2EE apps via the WEB-INF/lib directory. Yes, you can use copy of the exported classes/interfaces there for the benefit of the app code, but typically in a J2EE appserver, the actual
running copy of the EJB is outside the webapp. That's why there's both WAR files and EAR files.
Regrettably, there's no real standard here, so you have to RTFM on how to deploy for your particular brand of appserver. In the JOnAS/Tomcat system I'm using, I simply softlink the EJB jars from the JOnAS deployed-ejb directory to the user library in Tomcat:
ln -s /usr/local/JONAS/ejbjars/myejb.jar /var/tomcat3/lib/apps/myejb.jar
Not necessarily the cleanest solution, but one that works until ObjectWeb comes up with something that eats EARs.
JBoss is better integrated with Tomcat for EJBs, but you'll have to read the docs for yourself - Its been so long, I've forgotten how it works.
... And yes, the "ln" command is for Linux, not Windows. You need at least Windows 2000 to be able to do something equivalent. Otherwise, just make 2 copies of the jar - 1 for the EJB server and one for Tomcat - unless JBoss does something nice for you.
[ July 23, 2002: Message edited by: Tim Holloway ]