Problems with XMLP's XSLT engine

Question

Hi,
To work around the limitations of the XMLP's builtin
crosstab support, I have included a XSL file
like <?import: file:///C:MakeTheTable.xsl?>
and used <xsl:call-template name="myTable">
to invoke the template and generate the XSL-FO
directly. Now the problem is that XMLP's XSLT
engine gives in some table cells wrong values
(compared to XML-Spy's XSLT engine and Microsoft
MSXML 4.0). Is there a way to assign XMLP's XSLT
engine as "external XSL transformation program" in
XML Spy?
I am using the "Preview - PDF" menu in WORD.
Is there a way to get the generated XSL-FO?
Thank you,
Heinz

Answer 1

Hi,
I used XMLP's Java API to write a little application that I can use as "external XSL transformation program" for XML Spy. My findings so far:
- XMLP's FO engine gives correct results, the problem is caused by XMLP's XSLT engine, that creates a bad FO-file.
- I tried a workaround, replaced a for-each loop with some XPath statements by an for-each-group, group-by, current-group(). I got a different result, but not the correct one :-(
Our motivation to look at XML Publisher was, that the cross-tab (matrix) support of
Oracle Reports was not very good, for that what we needed. I am beginning to get the
impression, that the cross-tab support of XML Publisher is even worse. Of course are
any positive, optimistic comments appreciated.
Heinz