Re: [JBoss-user] classpath confusion

[Guy Rouillier]

Don't put anything in classpath.  It's tempting, and it can make development easier, and you can probably get along fine for awhile.  But sooner or later, you'll get bizarre problems.  The most common is that updates to your EJBs don't take (i.e, they appear to deploy properly, but when you invoke methods on a new version, the old version is run.)  For 2.4.x, set JBOSS_CLASSPATH as required.  For 3.0, which I haven't used much, there are additional mechanisms for specifying required runtime jars. ----- Original Message ----- From: Frank Morton To: [EMAIL PROTECTED] Sent: Thursday, January 03, 2002 1:20 PM Subject: [JBoss-user] classpath confusion I have accumulated a lot of stuff in my CLASSPATH and JBOSS_CLASSPATH that probably doesn't need to be there. Advice on the forums seems to range from to not touch JBOSS_CLASSPATH to just pile everything into the two paths until it works, which is what I've done.   Does anyone really know what the "right" jar files should be included in CLASSPATH and JBOSS_CLASSPATH to both start the server and to start applications using the server?