If the XSLT terminates like that it means that your stylesheet isn't well-formed XML. Your XML editor should help you identify the problem. However, if I look at the XSLT, I can see that there is more than one problem. For example, there is an fo:block as direct child of an fo:table-header (right next to a xsl:if in line 297). That's illegal and will result in another error in FOP once you've fixed the well-formedness.
So: - fix well-formedness in the XSLT - then fix the FO errors reported by FOP. The -foout option will help you quickly seeing the problems in the generated FO. From there go back to the XSLT to fix the problems. Good luck! On 07.02.2008 14:40:50 Cristian Ferrero wrote: > Thank you Jeremias i did what you advice to me and now appears the error : > > javax.xml.transform.TransformerConfigurationException: > javax.xml.transform.Trans > formerConfigurationException: javax.xml.transform.TransformerException: > org.xml. > sax.SAXParseException: The element type "fo:table-cell" must be terminated > by th > e matching end-tag "</fo:table-cell>". > > > im new at this, my xsl is made under XSLFAST , where i can see the pdf > results with xml ...but with apache appears errors like this for example...i > need work with apache because i have to run xml to pdf conversion from java > aplication..exists really any application 100% compatible with apache fop > where i can design my template and just run it with apache or i have to > desist and make my xsl "manually".. > > i attach my xsl and my xml too.....thanks and sorry if i make dummy > questions--- > > > > ----- Original Message ----- > From: "Jeremias Maerki" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Thursday, February 07, 2008 9:51 AM > Subject: Re: Apache errors > > > You'll have a much easier time if you just run the XSLT transformation > without FOP. Then you can inspect the generated XSL-FO. That should help > you figure out the problem. On the command-line you can use the -foout > option instead of -pdf to just generated the XSL-FO file. > > BTW, posting an XSLT alone usually doesn't help because without knowing > how the XML looks like, most people won't even look at it because they > can't run it. > > Given the error message, you probably need to make sure in your XSLT > that you don't generate any table-cells if you don't have content for > them. As a dirty hack you can try to use the -r (relaxed validation) > option on the command-line. That will overlook empty table-cells. But > empty table-cells are illegal so you should avoid them using XSLT means. > That's why it's a dirty hack. > > Good luck! > > On 07.02.2008 12:57:50 Cristian Ferrero wrote: > > Hi again...i can' t complete my xsl - fo conversion because a couple of > > errors that i can't get wich is the reason, i made my xsl with XSL FAST, > > then i fix a few things that Apache fop needs , by still have a couple of > > errors and i can't get the reason... > > first is a warning : > > > > ADVERTENCIA: Mismatch: table-cell (http://www.w3.org/1999/XSL/Format) vs. > > root ( > > http://www.w3.org/1999/XSL/Format) > > > > > > another is an error : > > > > GRAVE: Exception > > javax.xml.transform.TransformerException: > > org.apache.fop.fo.ValidationException: > > Error(Unknown location): fo:table-cell is missing child elements. > > Required Content Model: marker* (%block;)+ > > at > > org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168) > > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > > at org.apache.fop.cli.Main.startFOP(Main.java:166) > > at org.apache.fop.cli.Main.main(Main.java:197) > > > > i attach my xsl...really thanks... > > > > > Jeremias Maerki > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
