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 2003/06/11 11:04:22 UTC
DO NOT REPLY [Bug 20675] New: -
Tomcat is not compliant with the JSP 1.2 specification.
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=20675>.
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=20675
Tomcat is not compliant with the JSP 1.2 specification.
Summary: Tomcat is not compliant with the JSP 1.2 specification.
Product: Tomcat 4
Version: 4.1.24
Platform: All
URL: http://none.right.now
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper 2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: sopel@freebsd.hbz.pl
Hello,
As:
http://java.sun.com/products/jsp/syntax/1.2/syntaxref1210.html#15653
says:
The page directive applies to an entire JSP page and any of its static include
files, which together are called a translation unit. A static include file is a
file whose content becomes part of the calling JSP page. The page directive does
not apply to any dynamic resources; see <jsp:include> for more information.
Yet, if we have page a.jsp and page b.jsp, a.jsp being:
----- begin a.jsp
<%@ page pageEncoding="ISO-8859-2" contentType="text/html;charset=ISO-8859-2"%>
<%@ include file="b.jsp" %>
<some native chars (iso-8859-2)>
---- end a.jsp
and b.jsp being:
---- begin b.jsp
<some native chars (iso-8859-2)>
---- end b.jsp
The native chars in b.jsp ARE NOT displayed correctly (only the ones in a.jsp
are displayed correctly).
I hope this is fixed once and for all in an upcoming tomcat release, please
notify me of the fix.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org