You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ben Boule <bb...@watercove.com> on 2002/07/31 00:05:46 UTC

Classpath Woes...

Hi, 
I was wondering if anyone could help me out with a problem with Tomcat
3.3.x.

We've developed our application under the Tomcat 3.2.x implementation that
is integrated into JBuilder 6.  We use Struts for our framework.  The
application works
fine in that environment.  I am now trying to set up the deployment, and we
wanted to 
use either Tomcat 3.3.x or Tomcat 4.0.x.    Tomcat 4 seems to have issues
with our 
ORB implementation (Borland) so for now I am working with 3.3.x.

The problem is that when the application goes to compile a .jsp file for the
first time, 
it encounters a ClassNotFoundException trying to find a Jasper class,
JspServlet.

e.x.  (from the std output)

2002-07-30 17:58:30 - Ctx(/<app name>) : Class not found:
org.apache.jasper.servlet.JspServlet

If I copy the jasper.jar file from $TOMCAT_HOME/lib/container into <app
name>/WEB-INF/lib, then the Jasper classes are not found.

However, this results in another class not found exception, this time it
can't find the classes for the javac compiler!   (sun.tools.something)

If I then copy the tools.jar file from the JDK 1.3 distribution into the
WEB-INF/lib directory, everything works.  This would obviously seem to be an
unacceptable solution however.

I can't figure out why this is happening.  It doesn't happen with the
example applications under the exact same environment.

(JAVA_HOME is set to point to JDK 1.3.1, TOMCAT_HOME is set to the right
directory as well.)

I have read the classloader-howto several times but I can't figure out
what's wrong.

Thanks,
Ben Boule



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>