DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11432>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11432 Branch target offset too large for short [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-08-02 19:53 ------- We have already done what we can on this problem. See http://xml.apache.org/xalan-j/xsltc_constraints.html#xsltcconf It says: In some cases, XSLTC can generate methods that are too long (> 64K length) to run, or contain jump offsets that are too large for the JVM to handle. You can minimize this by breaking up large templates into smaller templates. XSLTC has a new compile option to disable template inlining, compiling each template in a separate method. From the command line, you would use "-n" to turn offinlining, or with TrAX set the "disable-inlining" attribute to the TransformationFactory. For example, TransformationFactory tfac = new TransformationFactory(); tfac.setAttribute("disable-inlining", new Boolean(true))
