-
1. Re: "Class not found" while deploying
ioparra Jul 18, 2003 2:28 PM (in response to marcomanco)I get that if the ejb.jar that I'm deploying is dependent on a different jar that has not been deployed yet.
Try removing just this ejb.jar, start up jboss(wait for the full/clean start up), then drop your ejb.jar in. If you don't see this problem, then its a deployment ordering issue. If you do...
-Ivan -
2. Re: "Class not found" while deploying
marcomanco Jul 22, 2003 2:43 AM (in response to marcomanco)the problem is that I don't have all classes in the deploy-directory, I have also some libs in my classpath. The JBoss-Server is not able to find the classes from the classpath...
And the classpath I set is definitely correct.
The package-structure in the jar in the deploy-directory of the server is identical to the package in the jar from the classpath. Could this be a problem? -
3. Re: "Class not found" while deploying
juhalindfors Jul 22, 2003 4:59 AM (in response to marcomanco)Using the system classpath is definitely not recommended with JBoss.
-- Juha -
4. Re: "Class not found" while deploying
ioparra Jul 22, 2003 2:30 PM (in response to marcomanco)I agree, classpath is a "no-no". Your choices are simple.
Place the jar in the server/default/lib directory
or
server/default/deploy
You could choose the jboss/lib directory as well. I'd prefer the deploy directory for the hotdeployment feature, or the lib directory if you don't plan to hotdeploy. -
5. Re: "Class not found" while deploying
frito Jul 23, 2003 1:58 AM (in response to marcomanco)Good practice:
put everything in the deploy directory, as ioparra told you. I would suggest another way: deploy an ear with all your jars. Use the Class-Path of the manifest of your ejb jar.
Greetings,
Frito