[Happy Independence Day fellow Americans!] Manuel Mall wrote:
Looking at the stylesheet you seem to simply generate a table. IMO if this is all you want to do FOP may not be the best tool for the task at hand. For example storing your test results in a database and using a report writer may be a much better fit to your needs. The strength of FOP is NOT in the generation of hundreds of pages of identically structured tabular data. FOP is actually fairly inefficient at doing that.
While FOP may indeed not be optimized or designed to handle generating the telephone book of a large city, I think we should stress that this is not necessarily a limitation of XSL or XSLT.
XSL and XSLT combined still offer incredible power in allowing you to implement the "Don't Repeat Yourself" principle--common headers and footers and formatting rules, etc., that normally would have to be defined and maintained individually within each report using a traditional report writer can be stored and maintained in just one place. As the number of reports increases, the maintenance savings from using xsl:import, xsl:include, xsl:call-template, etc., grows exponentially over reporting tools that generate must-be-maintained-individually reports.
So I personally would be more inclined to (1) make sure the user really needs a report as large as the one they are generating (most people won't read 1000-page reports anyway, for example) and, if so, (2) first refer the user to a commercial XSL FO processor if they are doing something beyond FOP's capabilities, not to a manual WYSIWYG-like 4GL report generator.
Glen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
