Gaining OutOfMemoryException during transforming
Hi guys, I got a strange problem during transforming XML and a XSLT to PDF. Using Version 0.20.5 of FOP. First, I create accountstatements, i.e. for GL accounts, Debitor accounts or Creditor accounts. The XML output for all GL accounts in one month is nearly 10 MB large. Debitor/Creditor accounts of one month is much bigger, nearly 15 MB. While transforming the Debitor/Creditor XML to PDF, there is no problem. The CPU usage rises up to 100%, but the rendering successes. But with the smaller GL accounts XML I get an OutOfMemoryException. What could be the reason? BR... Sahin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gaining OutOfMemoryException during transforming
Chris Bowditch schrieb: Ail Sahin wrote: Hi guys, I got a strange problem during transforming XML and a XSLT to PDF. Using Version 0.20.5 of FOP. First, I create accountstatements, i.e. for GL accounts, Debitor accounts or Creditor accounts. The XML output for all GL accounts in one month is nearly 10 MB large. Debitor/Creditor accounts of one month is much bigger, nearly 15 MB. While transforming the Debitor/Creditor XML to PDF, there is no problem. The CPU usage rises up to 100%, but the rendering successes. But with the smaller GL accounts XML I get an OutOfMemoryException. Well the actual FO size is not stricly directly proportional to memory usage. It's slightly more complex than that. Memory usage depends on the exact FO used. For example, fo:table and nested tables in particular are very expensive in terms of memory and CPU. You're right, there are a lot of tables in the FO. But how could I manage design an account statement without tables? It may also be that the FO for GL, has just one page-sequence whilst the Debitor/Creditor accounts are split up into multiple page-sequences. That's the funny thing: It's all the same FO. Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gaining OutOfMemoryException during transforming
Chris Bowditch schrieb: There are several options open to you: 1) increase JVM heap size. 2) try it on FOP 0.91beta and see if problem remains 3) download latest code from SVN maintenance branch. There were some changes made since 0.20.5 specifically aimed at reducing memory consumption of tables. Thanks a lot for your answers, by the way. I realized that my FO doesn't work with FOP 0.91beta. Seems that I have to do some modifications on it. Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gaining OutOfMemoryException during transforming
Chris Bowditch schrieb: Just to be clear: In answer (3) I'm not talking about FOP 0.91beta or similar, I was referring to a 0.20.6 available as code only using SVN. Sorry for my noob question, but what is SVN? Found only code for FOP 0.91beta in the Trunk. Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gaining OutOfMemoryException during transforming
Chris Bowditch schrieb: Ail Sahin wrote: Chris Bowditch schrieb: Just to be clear: In answer (3) I'm not talking about FOP 0.91beta or similar, I was referring to a 0.20.6 available as code only using SVN. Sorry for my noob question, but what is SVN? Found only code for FOP 0.91beta in the Trunk. No problem. SVN is source code repository. FOP 0.91beta was generated from the trunk. However there is a branch for 0.20.x, which you should download the unreleased code from. Point your SVN client to the URL: http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_20_2-maintain I got it. Thank you very much. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: region-body problem
Chris Bowditch schrieb: There is an example on the website: http://xmlgraphics.apache.org/fop/fo.html#fo-first-page Thanks a lot for that link. It helped me get out of the mud ^^ Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Empty lines
Hi there, look at the following snippet fo:block break-before=page font-size=10pt font-weight=bold space-after=1cm xsl:value-of select=name2/fo:block/xsl:text/xsl:text xsl:value-of select=street/fo:block/xsl:text/xsl:text xsl:value-of select=postalcode/xsl:value-of select=city/xsl:text/xsl:text /fo:block I'd like to have three empty lines before name2. Any ideas how to manage this? Thanks in advance Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Forcing Whitespace
Hi there, I have following block fo:block break-before=page font-size=8pt font-weight=normal space-before=3cm xsl:value-of select=sender/title/xsl:text /xsl:text xsl:value-of select=sender/name1/xsl:text /xsl:text xsl:value-of select=sender/name2/xsl:text /xsl:text xsl:value-of select=sender/name3/xsl:text /xsl:text xsl:value-of select=sender/postbox/xsl:text /xsl:text xsl:value-of select=sender/street/xsl:text /xsl:text xsl:value-of select=sender/state/xsl:text /xsl:text xsl:value-of select=sender/country/xsl:text /xsl:text xsl:value-of select=sender/postalcode/xsl:text /xsl:text xsl:value-of select=sender/city/fo:block/xsl:text /xsl:text fo:leader leader-pattern=rule / /fo:block I'd like to have some whitespaces between each xsl:value-of How to manage this? Greets Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forcing Whitespace
Simon Burton schrieb: Putting a space between xsl:text tags does add a single char of whitespace - do you mean you want several chars of whitespace between them? That does not work. I'd like the address to be Prename Surname Address Postalcode City in one single line. But my sheet version does sth. like PrenameSurnameAddressPostalcodeCity in one single line. You can add white-space-collapse=false to your block tags Already tried. Without success. if you want more white space you may need to add some non breaking space references (nbsp;) but they have to be outside of xsl:text tags. Tried but got following error message: The entity nbsp was referenced, but not declared. - Start Original Message - From: Ail Sahin [EMAIL PROTECTED] To: fop-users@xmlgraphics.apache.org Subject: Forcing Whitespace Hi there, I have following block fo:block break-before=page font-size=8pt font-weight=normal space-before=3cm xsl:value-of select=sender/title/xsl:text /xsl:text xsl:value-of select=sender/name1/xsl:text /xsl:text xsl:value-of select=sender/name2/xsl:text /xsl:text xsl:value-of select=sender/name3/xsl:text /xsl:text xsl:value-of select=sender/postbox/xsl:text /xsl:text xsl:value-of select=sender/street/xsl:text /xsl:text xsl:value-of select=sender/state/xsl:text /xsl:text xsl:value-of select=sender/country/xsl:text /xsl:text xsl:value-of select=sender/postalcode/xsl:text /xsl:text xsl:value-of select=sender/city/fo:block/xsl:text /xsl:text fo:leader leader-pattern=rule / /fo:block I'd like to have some whitespaces between each xsl:value-of How to manage this? Greets Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - End Original Message - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
region-body problem
Hi there, I have an stylesheet with a region-before and a region-body. The region-before extents at 8cm, because it's an area where the reveicers address is written. the region body has a margin-top of 7cm. When there is a page-break, the region-body starts at 7cm. Is there a way to say that the region-body should start at 7cm only on the first page? BR... Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Letter in xsl
Thanks a lot, I'm gonna trying it right now. Glen Mazza schrieb: Ail Sahin wrote: One 'page' is one customer with its n-Vouchers. The first page should contain receipient address, subject, columnnames, text etc and the list of vouchers. That works fine but when there are many vouchers, a second page ist printed, but with the receipient adress, subject etc. I guess the problem is that you do *not* want the header information on pages after the first. I think you will need to create an fo:page-sequence-master for this to work. Do a search on page-position=first here [1] for the general idea. Next, very similar to here [2], you'll be activating different fo:simple-page-masters based on whether or not the page is the first in the page sequence. Instead of left or right, however, the issue is first-page or not first-page. [1] http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/pagination/franklin_2pageseqs.fo?rev=197469view=markup [2] http://marc.theaimsgroup.com/?l=fop-userm=113078517606736w=2 Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Letter in xsl
Hi there, I have some problems creating a certain XSL:FO file. I'd like to create series letters respective account statements for n-customers. The XML-Data is managed like followed: data page name Mr. X /name street X-Street 1 /street city Ownedtown /city header Accountstatement /header maintext Foo Bar /maintext column0 Documentnumber /column0 column1 Documenttext /column1 column2 Debit/Credit /column2 body voucher docnumber 1 /docnumber doctext Invoice /doctext amount 100 /amount /voucher . n-vouchers . voucher docnumber 100 /docnumber doctext Invoice /doctext amount 120 /amount /voucher /body /page page same as obove /page /data One 'page' is one customer with its n-Vouchers. The first page should contain receipient address, subject, columnnames, text etc and the list of vouchers. That works fine but when there are many vouchers, a second page ist printed, but with the receipient adress, subject etc. How to handle this?` The XSL-File: xsl:template match =/ fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-reference=main page-height=29.7cm page-width=21cm margin-top=6.0cm margin-bottom=1.5cm margin-left=1.5cm margin-right=1.5cm fo:region-before extent=8.0cm/ fo:region-after extent=2.0cm/ fo:region-body margin-top=7.0cm margin-bottom=0.5cm/ /fo:simple-page-master /fo:layout-master-set xsl:for-each select=data/page fo:page-sequence master-name=main initial-page-number=1 fo:static-content flow-name=xsl-region-before fo:table table-layout=fixed padding=3pt fo:table-column column-width=10cm/ fo:table-column column-width=8cm/ fo:table-header fo:table-row fo:table-cell fo:block text-align=left font-size=10pt font-family=Courier line-height=14pt xsl:apply-templates select=title/ fo:block/fo:block xsl:apply-templates select=name1/ fo:block/fo:block xsl:apply-templates select=name2/ fo:block/fo:block xsl:apply-templates select=street/ fo:block/fo:block xsl:apply-templates select=postalcode/xsl:apply-templates select=city/ /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell number-columns-spanned=2 fo:block font-family=Courier font-size=10pt text-align=left xsl:apply-templates select=header/ /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell number-columns-spanned=2 fo:block font-family=Courier font-size=10pt text-align=left xsl:apply-templates select=maintext/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table fo:table table-layout=fixed padding=1pt fo:table-column column-width=2.6cm/ fo:table-column column-width=2.0cm/ fo:table-column column-width=2.3cm/
