Reply inline -
Nathan S. Haigh wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Smith wrote:
Hi Nathan.
If setup properly, the location of your webapp shouldn't cause issues
with finding various classes. Just don't mention that dirty, dirty word
CLASSPATH :-). Seriously messing with the CLASSPATH environment
variable will cause loads of headaches. Best to just not mess with it
and let tomcat ignore it.
That's fine - I haven't touched it! :)
Just making sure. I cringe when I see that word -- it always brings
trouble.
You can find information on tomcat's classloader structure at
http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html
(assuming you are using tomcat 5.5). Each version of tomcat has it's
own version of this document.
I recently installed tomcat 6.0.13 and running with JVM version 1.6.0_01-b06
I'll have a look at this doc now.
Then the default classloader structure will be simpler than what was in
tomcat 5.5. The two important directories will be your webapp's
WEB-INF/lib folder and tomcat's own /lib folder.
The errors you are getting indicate your webapp can't find
commons-fileupload.jar and commons-io.jar. Those should be stored in
WEB-INF/lib of your webapp.
here are the files in WEB-INF/lib:
commons-fileupload-1.1.1.jar
commons-io-1.2.jar
mysql-connector-java-3.1.10-bin.jar
does it matter they have their version number in their filenames?
Nope. The name of the jars makes no impact (other than they have to
have the .jar file extension). Check permissions. Best way I've found
is to sudo to the tomcat user account and attempt to access the jars in
your webapp. Then you'll get the exact same response in your terminal
shell that tomcat would get.
Also your log indicates you have packages declared the same name as some
of your classes. Modify, MassList, Mass, Adducts, and AdductList should
be declared to be of package db, not db.Modify for example. Same goes
for masIO.FileHandler -- should be declared of package massIO, not
massIO.FileHandler.
I think you may be incorrect with this. I have double checked, and they
are all declared as the correct package and not as package.class as you
suggest (unless I misunderstand). e.g. at the top of my
massIO.FileHandler class I have:
"package massIO;"
Is this what you mean?
Well.. yes. The error about trying to use a package name as a type has
to come from somewhere. I've never seen it show up unless the jvm is
really finding a package name matching the declared type. Not knowing
more about your setup, I'll let you explore that one.
Also, one thing that puzzles me, is that this works fine in the tomcat
installation webapp dir at /usr/local/tomcat/webapps/appname
But not under public_html in a user's directory.
Well... my last thought is there is another webapp of the same name
visible to tomcat and there's some confusion about which one is active.
Make sure the one you had in tomcat's webapps directory is really gone
and you have restarted tomcat. Also make sure you don't have a
appname.xml file in the conf/Catalina/localhost directory of tomcat
conflicting with your webapp in public_html.
--David
I'll read that webpage while I await a response.
Thanks
Nath
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGeTSJczuW2jkwy2gRAiypAKC3jKW0s/6ZerYCE5dgnJWVz8vcTgCglzy3
MGoahlleptf24M+0fTICy6g=
=7CSs
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
