> -----Original Message----- > From: David Graham [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 05, 2003 8:43 AM > To: [EMAIL PROTECTED] > Subject: Re: [OT] Java method size limitations > > This came up before in relation to tomcat's jsp compiler > generating large methods. I believe they now break up > methods into smaller pieces to avoid the limitation. > Regardless, I can't think of any good reason to have an > 8500 line class!
First off, Tomcat has indeed fixed this problem. Jasper now translates custom tag calls into private methods, instead of just inlining them in the _jspService method. But some servlet containers (*cough*Dynamo*cough*) throw *everything* in the _jspService method. So you could have a really tight, well designed page -- no scriplets, all tags, tiled, etc. -- and, if you have a lot of tags or other "hidden" code, it will still blow up because of the way the container performs it's JSP --> .java translation. And you won't know it until runtime. This is really frustrating when you encounter it on supposedly enterprise level containers. If it's really enterprise level, you'd think they'd have less of a brain dead translation engine. In any case, I remember looking over the list of items for Java 1.5 and the upper limit on jumps was something that was being addressed. -= J --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
