It is my understanding that Java still has a limit of only 64K for each method. This doesn't allow some of our JSP files to be compiled into servlets, because the service method would go over the limit.
Our JSP pages are large government forms, which typically scroll through several screenfuls of information (the HTML file is typically around 150K in size and Struts undoubtably further adds to this size). Since these are government forms (think IRS 1040), users expect a certain visual presentation (a single long form). So from a design viewpoint, breaking these forms into different physical pages isn't an acceptable solution from the customer's viewpoint. I am looking for design strategies for partitioning the method so that it doesn't effect the visual presentation and doesn't lead to incredibly ugly unmaintainable code. Thanks, Norman -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
