I'm working on a project where a client has requested being able to run our web application on Oracle 10gAS. Currently our web application has been exclusively deployed to
Tomcat 4.1.30.
In loading up and
testing on 10gAS, I have discovered about 5
JSP pages that do not compile, giving me errors about the code being to large in a try block. A look at the .java files being generated shows that about 80-90% of the page is being wrapped in one huge try-catch block (unlike what Tomcat does - tomcat breaks quite a bit of the code out into seperate methods).
Is there any way to force the OC4J pieces to break up the code?
I can certainly go through the 5 or 6 pages and break it up myself using <%! %> blocks to declare methods and <jsp:include > for some of the static pieces, but I'd rather not make all the pages really unreadable and hard to maintain just because Oracle's system is dumb enough to try and wrap the majority of a JSP page in a single block of code.