Re: Namespace not found error when trying to generate PDF in Servlet using FOP

[John Quinn]

Okay, saxon is now running under JBoss.  I still fail at the same line with the following error now:

13:57:58,102 INFO  [PDFReport] PDFReport code source for TransformerFactory: (fi
le:/opt/opensource/jboss-4.0.3SP1/server/test1/tmp/deploy/tmp14491teaa.war/WEB-I
NF/lib/saxon.jar <no certificates>)
13:57:58,103 INFO  [PDFReport] PDFReport package for TransformerFactory: package
 com.icl.saxon
13:57:58,406 INFO  [STDOUT] Error on line 37 column 81 of null:
  Error reported by XML parser: The entity name must immediately follow the '&'
in the entity reference.
13:57:58,409 ERROR [PDFServlet] Error generating PDF file
javax.xml.transform.TransformerConfigurationException: Failed to parse styleshee
t
        at com.icl.saxon.PreparedStyleSheet.prepare(PreparedStyleSheet.java:119)
        at com.icl.saxon.TransformerFactoryImpl.newTemplates (TransformerFactoryI
mpl.java:127)
        at com.kroger.accounting.ad.reports.PDFReport.generate(PDFReport.java:98
)
        at com.kroger.accounting.ad.view.reports.PDFServlet.generateReport(PDFSe
rvlet.java :80)
        at com.kroger.accounting.ad.view.reports.PDFServlet.doGet(PDFServlet.jav
a:70)

 

I'm not sure why it is failing on line 37.  The xsl file line 37 is below:

<fo:page-sequence-master master-name="report">

 

The error first states:

 Error on line 37 column 81 of null:
  Error reported by XML parser: The entity name must immediately follow the '&'
in the entity reference.
 

 

But I don't know why it talks about null, and the only '&' in the file are of the following nature:

<fo:list-item-body start-indent="body-start()">

        <fo:block white-space-collapse="false">

                <xsl:value-of select="VendorNumber"/><xsl:text>&#xA0;</xsl:text>

        </fo:block>

</fo:list-item-body>

 

and those statements aren't even close to line 37 of the  xsl file (which is what is being placed in the Stream on line 98 of PDFReport):

Templates xslTemplate = tf.newTemplates(new StreamSource(xslInputStream));

Does the null reference make sense to anyone in light of the error I have from Saxon?

Thanks,
John

 

On 4/14/06, John Quinn <[EMAIL PROTECTED]> wrote:

I found it on saxon.sourceforge.net:

Saxon 6.5.4 dropped support for certain rarely-used features of Saxon 6.5.3, notably support for JDK 1.1 and the Microsoft Java VM, support for FOP integration, and the applet interface. Users requiring these features should continue to use version 6.5.3.

 

I'll try forcing Xerces on Saxon.

 

Thanks,

John

 

On 4/13/06, Jeremias Maerki <[EMAIL PROTECTED] > wrote:

Where did you find something that says only SAXON 6.5.3 is compatible
with FOP? FOP should work fine with any XML Parser and XSLT
implementation as long as it implements the JAXP API and does not have
any strange bugs. You can also try to force SAXON to use Xerces by
setting the "javax.xml.parsers.SAXParserFactory" system property to
"org.apache.xerces.jaxp.SAXParserFactoryImpl".

On 13.04.2006 16:49:51 John Quinn wrote:
> I have tried using Saxon, but the application throws a config exception at
> that point because the commons digester must check for a validating
> parser and it say the aelfred sax parser implementation is not such a parser
> (packaged with Saxon 6.5.3):
>
> javax.xml.parsers.ParserConfigurationException: AElfred parser is
> non-validating
>
> at com.icl.saxon.aelfred.SAXParserFactoryImpl.newSAXParser(
> SAXParserFactoryImpl.java:34)
>
> at org.apache.commons.digester.Digester.getParser(Digester.java:686)
>
> at org.apache.commons.digester.Digester.getXMLReader (Digester.java:902)
>
> at org.apache.commons.digester.Digester.parse(Digester.java:1548)
>
> at org.apache.struts.action.ActionServlet.parseModuleConfigFile(
> ActionServlet.java:708)
>
> at org.apache.struts.action.ActionServlet.initModuleConfig(
> ActionServlet.java:670)
>
> at org.apache.struts.action.ActionServlet.init(ActionServlet.java:329)
>
> at javax.servlet.GenericServlet.init (GenericServlet.java:211)
> This is version6.5.3  of Saxon, as this is the version the documentation
> pointed to as being compatible with FOP.  But clearly not compatible with
> JBoss and the application.
>
> Any other ideas on how to clear up the Namespace problem.
<snip/>


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]