https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #4 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to Mark Thomas from comment #3) > It should be possible to analyse you generated clss files to see how big > they are. In this case, the compiler is failing, so no .class file is generated. Only the auto-generated Java source can be reviewed. The only way to prevent this from happening is to somewhat arbitrarily divide the generated code for a JSP into sections that are unlikely to result in a method-size overflow. That path is fraught with difficulty. An automated approach may not be practical. Björn, I recommend that you look into using Tomcat's precompiler to either actually precompile your JSPs, or just as a sanity-check during your development process to determine if you are going to have any issues with JSP sizes. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
