why tomcat is still looking for old jar files?

Please help me it is a very serious problem.

I updated one of the jar files used by the project. I am using a new method that is available only in the new library. I removed the old jar files in my local system, and everything worked fine. Then I commit those files to the subversion, which is in the testing server, and then I created the war file. The war is successfully created, then I deployed to the tomcat. But, now there is an error in the portion I am using the method that is only available in the new jar files.

One of the error when I go to that portion is:

1. No Such Method Exists

The other errors on log files are:

1.

WARNING: Failed to open JAR

java.util.zip.ZipException: No such file or directory

2.

validateJarFile(tomcat/webapps/ROOT/WEB-INF/lib/j2ee.jar) - jar not loaded. See Servlet Spe

c 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class

Please help me, I have tried every other way to solve this. I have tried removing all the old jar files there were, and replacing with the new one. I have tried creating a war file and ftping to the testing server.

I problem is still there and it is because the testing server's tomcat is still looking for old jar files. I used Netbeans and add jar files as usual method.

[1335 byte] By [WillRubyKillJavaa] at [2007-11-26 22:28:30]
# 1
Check the contents of your WAR file that you are deploying on the testing server to see if it contains the JAR that you can't find.More than likely you are building your WAR file and your new JAR file is not being included in the build.
maple_shafta at 2007-7-10 11:31:41 > top of Java-index,Desktop,Deploying...
# 2
There is a jar file in the war file I am building. I also copied the new jar file to every place there was a old jar files. But, it cannot find out.
WillRubyKillJavaa at 2007-7-10 11:31:41 > top of Java-index,Desktop,Deploying...
# 3
Did you completely remove every occurence of the old jar file from your testing server? Somehow your testing server is finding the old jar file first on the classpath and using that in place of your new jar file.
maple_shafta at 2007-7-10 11:31:41 > top of Java-index,Desktop,Deploying...