You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/03/28 08:11:00 UTC
DO NOT REPLY [Bug 7559] New: -
Explicit import required for JSP pages
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7559>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7559
Explicit import required for JSP pages
Summary: Explicit import required for JSP pages
Product: Tomcat 4
Version: 4.0.3 Final
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: tine@widelabs.net
As reported at http://www.jguru.com/faq/view.jsp?EID=753900 and it's true.
But before I found this, it took be a few hours to deal with this kind of
problem (an it could take me more).
Tomcat 4.0.x "Class org.apache.jsp.{Class} not found??
In Tomcat 4.0.x, all jsp pages are running as part of the org.apache.jsp
package.
If you use any class that hasn't been imported, the jsp compiler is expecting
it to be in the same org.apache.jsp package.
If a class does not belong to any package (so, for example, it is phisically
located in WEB-INF/classes), it must be imported:
<%@ page import="MyClass" %>
This is different from previous versions of Tomcat where that esplicit import
wasn't required (even if there were some cases where that wasn't completely
true).
Maybe just a short explaination can do.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>