Great! Glad to see it working. I would still find the time to refactor
your code and remove the dependencies on specific directories though.
The new classloader is so much nicer than the old classpath system.
--David
Sam Halicke wrote:
It ended up being the CLASSPATH environment variable,
Hi all, first time posting to the list.
I'm having several problems migrating JSPs and class/jar files to Tomcat
5.5.7 from Tomcat 3. I understand this is a big move, but I'm trying to
avoid any rewrite of the JSPs themselves. Documentation for tomcat 5.5.x is
rather sparse and terribly cryptic.
Hi,
One of the things you have to do is put support
classes for jsp in a package. I dont recall when those
requirements has changed.
aka_sergio
--- Sam Halicke [EMAIL PROTECTED] wrote:
Hi all, first time posting to the list.
I'm having several problems migrating JSPs and
class/jar
at the beginning, could the
path of that itself be a problem?
-Original Message-
From: sven morales [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 15, 2005 12:26 PM
To: Tomcat Users List
Subject: Re: Several configuration issues with Tomcat 5.5.7/Apache2
compiling JSPs
Hi,
One
Forget classpath -- it's ignored in Tomcat 5.5 and as I remember, was
being phased out in Tomcat 3 (wow -- have I been reading these mail
lists for that long??).
If you put your classes and jars in the right places, they will be
found. In your case, the classes are being found, but some
From: Sam Halicke [mailto:[EMAIL PROTECTED]
Subject: RE: Several configuration issues with Tomcat 5.5.7/Apache2 compiling
JSPs
Again, putting support classes for jsp in a package is
rather cryptic.
The term package in this instance refers to the Java language package
statement, which
It ended up being the CLASSPATH environment variable, which i suspected all
along.
Since our underlying code (some of it poorly written AFAIK, based on Tomcat
3 and the older JSP spec) relies on classes/jars being at a certain path in
the directory tree, copying the classes over to the WEB-INF
