Hello,
I'm trying to run FOP 0.20.4 on an IBM OS/390 mainframe, running under Unix
System Services. I also use Saxon as the XML parser and XSL transformer.
I get this error:
Error at byte 3 of
file:/u/tsryana/LMR/StandardRpts/xsl/StandardReportsPDF.xsl:
Error reported by XML parser: invalid
I fixed the problem below. When FTP'ing the style sheets to the mainframe,
I had to use binary mode instead of ascii.
Thanks to everybody for the replies!
Try Excelsior's JET product, it might be more user friendly:
http://www.excelsior-usa.com/home.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I'm trying to use FOP 0.20.4 in a multi-threaded environment to produce
PDFs. As I increase the number of threads from one or two to three or
four, the average rendering time per PDF increases significantly.
I realize that the host environment (available memory, number of
processors, etc etc)
I have FOP running on a Pentium 4 2.54 GHz computer with 1 GB memory and
Win2000. I use Saxon 6.5.2 as the XML parser and XSLT engine. It also
uses custom XMLReaders to produce SAX events which are processed by FOP.
We usually see a PDF production rate of 8-9 pages per second, and we
sometimes
We use XSLTC. I learned Java XML use and JAXP from an O'Reilly book
entitled Java and XSLT by Eric Burke. It includes an example of a
stylesheet cache that I found quite useful. Buy the book and check it out.
The recent posts about FOP running out of memory has me thinking.
Suppose for a second that FOP is run on a Windows 2000 box. Assume the box
has 512 MB of RAM. Pretend that a certain XSL-FO causes the JVM to run out
of memory.
The question is: Can the JVM heap size be set to a value larger
