-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave,

Dave Newton wrote:
> --- Mike Baroukh <[EMAIL PROTECTED]> wrote:
>> jdk5 should not have the problem.
> 
> Did 1.5+ remove the 64K limitation?

The 64k is a limit for method bodies, not try/catch. It should still be
very much in force:
http://java.sun.com/docs/books/jvms/second_edition/html/ClassFile.doc.html#88659

I must admit that I've never heard of this "try/catch too big" problem
before.

Since the "code" and "exceptions" attributes of a method in a Java
.class file have the same limitations (64k), and the compiler checks the
try/catch limits before the code limits, then they really are the same
thing.

In either case, those limits are still in force (i.e. you cann't exceed
64k of code, try/catch or not).

This is one of those irritating issues that breaks down the facade that
JSP operates behind. JSP authors shouldn't have to worry about the
limitations of Java when authoring their pages, but they do :(

>> There may be or may be no code added for the validation. But this
>> is not the problem ...
> 
> Technically, no, but it's the gating issue in this case.
> 
> Try breaking up the JSP into dynamic includes (which will be easier
> to manage anyway, because 100 fields on a form is *way* too many, and
> must make editing/modifying a nightmare).

This might not help, depending in which type of include you use. Static
includes, for example, will just import the code from the included JSP,
solving nothing.

Simplifying the page is definitely a good idea, though. If you use a lot
of taglibs (such as emitting 100 form fields using Struts tags), you'll
get a lot of generated code, causing you to run out of space.

The validation is not the problem, though. If you removed validation
entirely, you'd still get this error.

- -chris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF9twQ9CaO5/Lv0PARAgX3AJ9CJTPbkAF7nQ5EJQ5bTjiGUPmtAACggJ+H
OvylAQkRLgU70hRGJUzcpXo=
=rObM
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to