Compiling large stylesheet with XSLTC fails

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

Compiling large stylesheet with XSLTC fails

Compiling large stylesheet with XSLTC fails

2006-06-08 - By Joanne Tong

Reply: 1 2 3 4 5 6 7 8

Try rebuilding XSLTC with the latest source from Subversion. A patch was
recently committed to avoid the 64kb method size limitation. The patch
should fix some instances of the problem, though not all.
http://issues.apache.org/jira/browse/XALANJ-1324

If that doesn't work, try breaking up templates into smaller named
templates and use xsl:call-template.

Joanne Tong
Software Developer, XSLT Development, IBM Toronto Lab

"Sterritt, Christopher L." <chris.sterritt@(protected)>
06/07/2006 04:27 PM

To
<xalan-j-users@(protected)>
cc

Subject
Compiling large stylesheet with XSLTC fails

Hello,

We've got a stylesheet broken into parts which are
<xsl:include>'d. This was fine for the first bit, but with the second
bit (which is about 90k) now we can't run with XSLTC (although it all
works fine with just XSLT).

Is this a known issue with XSLTC? Are there workarounds
of any
kind, short of rewriting the code to call the stylesheets separately?
We've explicitly turned off inlining (I know it's the default, we had to
make sure) to make sure that's not the problem, and the result is the
same. We're facing a deadline, so the long-term goal of splitting above
the code that does the transform is reasonable, but not to hit our
deadline.

Thanks,
--chris sterritt

 Try rebuilding XSLTC with the latest
source from Subversion.  A patch was recently committed to avoid the
64kb method size limitation.  The patch should fix some instances
of the problem, though not all.
 http://issues.apache.org/jira/browse/XALANJ
-1324
 
 If that doesn't work, try breaking up
templates into smaller named templates and use xsl:call-template.
 
 
 Joanne Tong 
Software Developer, XSLT Development, IBM Toronto Lab 

 
 
 
<table width=100%>
<tr valign=top>
<td width=40%>"Sterritt, Christopher
L." <chris.sterritt@(protected)> 
06/07/2006 04:27 PM
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right>To</div>
<td><xalan-j-users@(protected)>
<tr valign=top>
<td>
<div align=right>cc</div>
<td>
<tr valign=top>
<td>
<div align=right>Subject</div>
<td>Compiling large stylesheet with XSLTC
fails</table>
 
<table>
<tr valign=top>
<td>
<td></table>
 </table>
 
 
 <tt>Hello, 
 
               
We've got a stylesheet broken into parts which are 
<xsl:include>'d.  This was fine for the first bit, but with
the second 
bit (which is about 90k) now we can't run with XSLTC (although it all 
works fine with just XSLT). 
 
               
Is this a known issue with XSLTC?  Are there workarounds of any 
kind, short of rewriting the code to call the stylesheets separately? 
We've explicitly turned off inlining (I know it's the default, we had to 
make sure) to make sure that's not the problem, and the result is the 
same.  We're facing a deadline, so the long-term goal of splitting
above 
the code that does the transform is reasonable, but not to hit our 
deadline. 
 
               
Thanks, 
               
--chris sterritt 
</tt>