Hello I inherited a java web application to support. Currently the application is in production and I am trying to build a developer environment for future changes. I am trying to run the application but I get the java.io.FileNotFoundException: error in the Java Console. It seems it is looking for retrotranslator-runtime-1.2.7.jar file which is in my Tomcat5\webapps\jars folder. I have modified my classpath by adding the path to the jar directory. But I still keep getting the same FileNotFoundException. I have check file permissions and it has read access to every account. Unfortunately there was no knowledge transfer with the previous developers. I was able to get some of the modules to work but not all of them. I am currently running Java6, Apache Tomcat 5 on Win XP environment. What else can I check for? Please advise.
You're not giving us much to go on, but are you sure the jar is being deployed where you think it is? It *looks* like an applet is trying to load the jar or something. Hard to tell with all the extra stuff in there.
The stack trace that you are showing us is from an applet.
Applets run on the client, not on the server, where Tomcat runs. If that applets needs a certain JAR file, the JAR file has to be made available at the client; it doesn't matter that it's in your Tomcat5\webapps\jars folder, because that's part of the server side Java code.
So it looks like the problem is on the client side where the applet is missing something; you'll have to focus on that, not on the server side Java code running in Tomcat.
It's long ago that I wrote an applet, so I don't remember the exact things you'd have to do to make a library available to an applet. Sun's tutorial about applets might be useful.
The directory layout of files is Tomcat5\webapps\fdis\jars. All my classes are in the jar files and I placed them on the jars directory in Tomcat.
posted 10 years ago
Be aware that "...FDIS..." and "...fdis..." are not the same.
posted 10 years ago
Yes, I am aware of the case sensitivity, but there is more to the application. The app uses Classic ASP, Microsoft's IIS, Apache Tomcat and a JK2 connector between IIS and Tomcat. In trying to set up a development environment on my XP desktop, I set up a default IIS web site with all caps "FDIS" to point to a local directory in my C drive that has all the ASP and html files. I also created a folder in the webapps folder in Tomcat called lower case "fdis" folder which has all the jar files. The way its suppose to work, the app loads the classic ASP page and based on what the user chooses calls another ASP page that has object declarations embeded in the ASP page. These make calls to Tomcat through the JK2 connector, which supposedly routes them to the jar files that are needed to launch the applet. I dont have experience with IIS talking with Tomcat but as you can see based on the stack trace I sent, the path it is using is
http://localhost/FDIS/fdis/jars. I dont know at this stage if this is correct given the environment I just described. But this is the path that it is trying to use to get to the jar files.
I did a trace on a production client machine that is accessing the application properly and got the following stack.
As you can see it differs there is no capital FDIS. I thought the "FDIS" is referring to IIS first then rerouting it to Tomcat to the "fdis" folder. Has anybody done anything similar to this? Since there was no knowledge transfer with the previous developers, minimal outdated documentation and no development environment, I am pretty much just guessing on how this is set up. Unfortunately we dont have access to the current production environment to see how things really should be set up.
This doesn't particularly seem to be a problem about applets. It's more about... well, I don't know. Tomcat? We have a forum for that. Would you like the post moved to that forum? It might get better (or at least different) answers over there. Let me know if you would.
posted 10 years ago
Yes, please if you can. Thank you.
It's a tiny ad only because the water is so cold.
Devious Experiments for a Truly Passive Greenhouse!