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=6088>. 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=6088 Too many custom tags? ------- Additional Comments From [EMAIL PROTECTED] 2002-01-31 14:11 ------- This is the typical error that occurs when the class file for a JSP gets too big, i.e. > 64K. I have yet to identify exactly what can not exceed 64K (my guess is a "{...}" block), but it is a limit imposed by the JVM. All Jasper based JSPs will reach this limit at some point when lots of tags are used. Tomcat 3.3 will hit the limit first because of some extra Tag pooling support that it has. The only way around it is to reduce the size of the JSP's class file by simplifying the page. Most likely we will need to "WONTFIX" this one when Tomcat 3.3.1 Final is released. You are welcome to attach a *simple* webapp containing the offending page so we can confirm there isn't some other problem. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
