No. The local .classpath is the Eclipse Java Build path. Edit it and you'll see what I mean.
When deployed, the servlet container (JBoss) determines the classpath, WEB-INF/lib etc.
Joined: Oct 27, 2010
I am sorry William I may not be asking the right question.
Should I build the entire .war file and redeposit it on the test server, if I have edited the .classpath?
the four (4) .jars that I have added to the project are as follows:
<classpathentry kind="lib" path="WebContent/WEB-INF/lib/esapi-2.0.1.jar"/>
<classpathentry kind="lib" path="WebContent/WEB-INF/lib/log4j-1.2.12.jar"/>
<classpathentry kind="lib" path="C:/jakarta-tomcat/lib/servlet.jar" sourcepath="C:/jakarta-tomcat/lib/servlet.jar"/>
<classpathentry kind="lib" path="C:/jakarta-tomcat/common/lib/servlet-api.jar"/>
To make it a bit more clear - when developing and deploying applications, there are multiple classpaths involved at various levels/stages. When you are developing an application you'll need compile/build time classpath references to various other libraries. If an IDE is involved it will have its own way of setting up this classpath. For Eclipse it's the .classpath file. If you aren't using an IDE then there will other build tools like Ant which have their own way of specifying classpath. All these classpaths are build/compile time classpaths and don't play a role when you deploy the application to a server like JBoss. So those .classpath files are of no relevance at that time.
The deployment/runtime classpath is determined by the packaging of your application. The Java EE spec has specific rules on how the dependent libraries should be packaged within the application and how they play a role in the runtime/deployment time classpath. For example, all jars in the .war/WEB-INF/lib of your application are available in the classpath of the application being deployed. There's also server specific ways of adding additional libraries to this classpath, but I won't go into those details since that's irrelevant.