Tomcat 4 puts the generated servlets for JSP pages it creates into package
"org.apache.jsp". Tomcat 3.2.3 did something different (which I don't
remember precisely), but that's OK because the spec explicitly allows
containers to put these classes wherever it wants.
The line in question would appear to be something you've included in a
scriptlet. The most likely explanation is that you didn't do an <%@ page
import="..." %> for the fully qualified class name of class
VersionTreeNode, so the Java compiler followed the rules in the Java
Language Specification, and assumed it was in the same class as the
calling page.
Craig
On Tue, 25 Sep 2001, Neeraj Vora wrote:
> Date: Tue, 25 Sep 2001 13:03:44 -0700
> From: Neeraj Vora <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: Tomcat 3.2.3 WAR files and 4.0
>
> Craig,
>
> Thanks for the info. Can you elaborate on the differences in the global
> class loading architectures? Seems like that is my problem.
>
> I'm getting the following error. The
> class it is complaining about is present in the WEB-INF/classes folder, but
> I don't understand why it is looking for it in the package org.apache.jsp.
> The same WAR file works without any problem on Tomcat-3.2.3.
>
> ***************************************
> org.apache.jasper.JasperException: Unable to compile class for JSP
>
> An error occured between lines: 23 and 40 in the jsp file: /main2.jsp
>
> Generated servlet error:
> C:\jakarta-tomcat-4.0\work\localhost\SoftSyncWeb\main2$jsp.java:14: Class
> org.apache.jsp.VersionTreeNode not found.
> private String printNode (VersionTreeNode vtn, String indentation,
> String reqURI)
> ^
> ***************************************
>
>
> >From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: <[EMAIL PROTECTED]>
> >Subject: Re: Tomcat 3.2.3 WAR files and 4.0
> >Date: Tue, 25 Sep 2001 12:21:17 -0700 (PDT)
> >
> >
> >
> >On Tue, 25 Sep 2001, Neeraj Vora wrote:
> >
> > > Date: Tue, 25 Sep 2001 09:13:08 -0700
> > > From: Neeraj Vora <[EMAIL PROTECTED]>
> > > Reply-To: [EMAIL PROTECTED]
> > > To: [EMAIL PROTECTED]
> > > Subject: Tomcat 3.2.3 WAR files and 4.0
> > >
> > > Are the Tomcat-3.2.3 Web-applications supposed to run as-is on
> >Tomcat-4.0? I
> > > have one that doesn't. Thanks..
> > >
> >
> >As long as your web apps are spec-compliant to the servlet 2.2 and JSP 1.1
> >specs, and don't rely on bugs or other non-spec behavior in 3.2.3, they
> >should indeed work. Failure to do so is a bug in Tomcat 4.
> >
> >The most likely causes for problems:
> >
> >* Your web.xml has elements not in the order required by the
> > DTD. Tomcat 3.2.3 accepted them anyway (even though it allowed
> > non-portable apps). Tomcat 4.0 uses a validating XML parser,
> > so your web.xml elements MUST match the required order.
> >
> >* Assumptions about the current working directory when running
> > Tomcat. This is never portable, and you should design your
> > applications not to rely on it.
> >
> >* Differences in the global class loading architectures.
> > You'll need to be more explicit about what your WAR file
> > does, and how it fails, to see if this is your issue.
> >
> >Craig
> >
>
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>
