Shapira, Yoav wrote:
This is why you should put your class in a package: http://jakarta.apache.org/tomcat/faq/classnotfound.html.
All of my form and action classes derive from abstract base classes based on ActionForm and Action. All of my application specific classes are packaged. I've verified this.
The class in question is being automatically generated by Tomcat when it tries to compile a JSP. AFAIK, there's nothing that I need to do w/respect to creating packages for JSPs and none of my JSPs are precompiled.
When I deploy the exact same webapp to WinXP w/Tomcat v4.1.30 & JDK v1.4.2 and NetWare v6.5 w/Tomcat v4.1.28 & JDK v1.4.2, the WAR file is unpacked OK at Tomcat startup and all of the JSPs are compiled successfully when the webapp is accessed for the first time. However, when I deploy the WAR file to OpenVMS Alpha v7.3-1 w/Tomcat v4.1.24 & JDK v1.4.2, the "login.jsp" file fails to be compiled into a Java class. I can see that "login_jsp.java" gets created, but there's no corresponding "login_jsp.class" file and this makes sense based on the error messages I'm seeing. The initial page to be accessed in the webapp is the welcome page, which is named "index.jsp" and it is located in the webapp's "root" folder. I can see that "index.jsp" was used to generate "index_jsp.java" and that was, in turn, compiled into "index_jsp.class" w/o any problems.
I'm still at a loss to explain why this happens on just this one Tomcat implementation.
-- Chuck Chopp
ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail 103 Autumn Hill Road 864 801 2774 fax Greer, SC 29651
Do not send me unsolicited commercial email.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
