Someone else may be able to help you 'around' this but chances are if you are hitting a limit of this kind you are doing way too much in a simple servlet.
I suggest you take a look at your code and try to apply a more Object Oriented style to it. Rather than just having one large procedure break it up into at least a few classes. This will help also for debugging, updating, and *maybe* reusability. HTH, Matt Quoting "Kenny G. Dubuisson, Jr." <[EMAIL PROTECTED]>: > I have a large servlet that has many try/catch areas in the code. When I > add my last piece of code in the last try/catch statement, I get the > following error when I try to compile: > > PtsReports.java:8224: code too large for try statement > catch (SQLException se) > ^ > > The try/catch area that is generating this error is smaller than some of the > other try/catch areas in the servlet. I've tried moving things around to no > avail. It looks like I've hit a servlet code limit but I was hoping someone > would know a way around it (like an option for the compiler). > > Thanks, > Kenny > > ___________________________________________________________________________ > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff SERVLET-INTEREST". > > Archives: http://archives.java.sun.com/archives/servlet-interest.html > Resources: http://java.sun.com/products/servlet/external-resources.html > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html > ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
