cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Engelhart <>
Subject Re: XSP size limit??
Date Thu, 27 Apr 2000 21:14:33 GMT
Ricardo Rocha wrote:

> Big XSP pages with a lot of static markup may easily generate Java classes
> whose "populateDocument" method exceeds the JVM-imposed 64K size limit:
> java.lang.ClassFormatError: Code of a method longer than 65535 bytes
Aha!  Thanks for figuring that out!!

> The main culprits:
> 1) lots of string constants in the generated method (element and attribute
> names, constant text nodes),
> 2) stack management code (xspParentNode, xspCurrentNode)
> Both of these problems will go away as we move towards a SAX-based
> XSP implementation in Cocoon2.
> Fixing this for Cocoon1 involves an extensive revision of the builtin
> "java-xsp.xsl" logicsheet, something we should probably defer in favor of
> working on Cocoon2's XSP implementation...

I wouldn't worry about it.  The array solution will work fine as a
workaround until we move to SAX in Cocoon2

thanks for the info.


View raw message