Altova Mailing List Archives


RE: [xsl] Fw: pdf file using xsl

From: "Michael Kay" <mike@------------>
To:
Date: 3/29/2006 6:06:00 PM
If your output file size is 200MB, then without knowing any details I would
expect the transformation to require at least 1Gb.

Michael Kay
http://www.saxonica.com/ 

> -----Original Message-----
> From: njain@xxxxxxx [mailto:njain@xxxxxxx] 
> Sent: 29 March 2006 16:49
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] Fw: pdf file using xsl
> 
> Hello,
> I tried this message earlier but it bounced back. I am new to this
>  I am working on an application which requires me to generate 
> a pdf file 
> of up to 200MB size. I tried generating xml file and then 
> apply xsl on it 
> with the Apache FOP driver.
>  
> The result is "Out of Memory" error. I am not sure where the 
> out of memory 
> error is coming, in FOP code or in Saxon8(I am using Saxon 
> processor and 
> XSLT 2.0).
>  
> Could anyone please help me out and let me know what could be wrong.
>  
> PS: I have already tried to increase the JVM memory (-Xms218m 
> -Xmx512m).
>  
> Regards.
> Neeraj

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.