DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31201>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31201 Encoding bug when using <jsp:include ...> action ------- Additional Comments From [EMAIL PROTECTED] 2004-10-11 02:46 ------- 1a.No I can't. So, I need this patch is committed. 1b.Please see API spec of RequestDispatcher#include method. (Because "jsp:include action" will be converted into this method.) This method must be able to handle any resource(such as a servlet, HTML file, or JSP file). But I feel like you said that because Tomcat cannot handle HTML file correctly, you ask to convert HTML file into JSP file. Isn't it right? 3.It can be resolved by defining DefaultServlet on each web app. If this patch is committed, we can separate web app from environment(locale) before fixing JSP spec. If you don't set file.encoding property, Tomcat will handle it just like former. So I believe there will be no demerit at all. If you say that property of i18n depending on container is a problem, see javaEncoding property of JspServlet. This property is also depend on the container, and assume that ALL JSP files for all webapps have the same encoding. Do you think that javaEncoding property is also a problem? Do you mean that it is not a problem, current Tomcat changes its handling by environments? I believe that this patch will be help for i18n problems, as other properties. Regards, Takayuki Kaneko --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
