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=24846>. 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=24846 Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug Summary: Quantity of org.apache.jasper.runtime.JspRuntimeLibrary.* usage triggers javac bug Product: Tomcat 5 Version: 5.0.14 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In Tomcat 5.0.14, for large JSP files with many includes, etc (producing a 94K .java file in this case), so many org.apache.jasper.runtime.JspRuntimeLibrary usages are generated that javac fails and reports an error stating "cannot resolve symbol". The symbol is "apache" and the location is "class java.lang.String" in a use of org.apache.jasper.runtime.JspRuntimeLibrary.include(request response "/some/path/someJsp.jsp", out true). Identical lines preceding this one did not produce compile complaints. This error is reproducible with javac from the command line with Java 2 v1.4.2_02 and 1.3.1_09 (the only 2 SDKs I have on the given system). The error goes away if one alters the source to import org.apache.jasper.runtime.JspRuntimeLibrary and use "JspRuntimeLibrary..." rather than the fully qualified package name! I understand the importance of avoiding namespace pollution, but being able to rely on JSP pages compiling is of higher importance than possible collision with "JspRuntimeLibrary"! I also understand this is Sun's bug, but a workaround in Jasper is a lot faster/easier than getting a javac bug fixed and available on all platforms. I would like to suggest adding org.apache.jasper.runtime.JspRuntimeLibrary to the list of imports in PageInfo's constructor (i.e. not as a standard import -- as it certainly is not but as an omni-present one all the same) and changing Generator to use "JspRuntimeLibrary" without package name qualifiers. If this change cannot be made in Tomcat 5.0.15 I'll be patching it into our packaging thereof but I believe it would be a very good idea to make this patch to 5.0.15 for everyone's sake! [The alternative is for Tomcat 5.0.x to get a reputation as not being robust in the face of large JSP files -- even if javac is actually at fault.] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
