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

[John Quinn]

The xml has no '&' in it.  It is formed directly from data that is extracted from the database.

 

Why I am focused on the xsl is due to the fact that it dies on this line:

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

)

 

and line 98 in PDFReport is this:

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

 

At this point, the template should have no knowledge of the xml that is to be transformed.  That doesn't happen until the xlst.transform call on the xml and xsl data as a DOMSource and StreamResult respectively.

 

So do you still think the xml could be the problem when it is creating the exception on this line?

Also, does the null cause a problem, or is this just an artifact of being created directly from the database data?

 

The xml generated is this ( This is the whole thing, I formatted this simple case, it is really one big line the way it is generated in the application):

<PORemittanceReport>
 <Comments></Comments>
 <DateOrdered>04/17/2006</DateOrdered>
        <DivisionCity></DivisionCity>
        <DivisionName>DIVISION-11</DivisionName>
        <DivisionState>OH</DivisionState>
        <DivisionStreet1></DivisionStreet1>
        <DivisionStreet2></DivisionStreet2>
 <DivisionZip></DivisionZip>
        <PoTotal>$1,000.00</PoTotal>
        <Pos>
  <PO>
   <Account>32-9976</Account>
   <Description>011-D00052-INSERTS</Description>
   <Event></Event>
   <EventDate>04/06/2006</EventDate>
   <EventDay></EventDay>
   <Market>ALL STORES</Market>
   <Period>03</Period>
   <PoAmount>$1,000.00</PoAmount>
   <PoDetails></PoDetails>
   <PoNumber>011000000058</PoNumber>
   <Year>2006</Year>
  </PO>
 </Pos>
 <UserFax>513-984-6709</UserFax>
 <UserName>advertising</UserName>
 <UserPhone>513-984-6700</UserPhone>
 <VendorCity>CAROLLTON</VendorCity>
 <VendorContactName></VendorContactName>
 <VendorFax></VendorFax>
 <VendorName>EAA NEWSPAPERS OF W. GEORGIA</VendorName>
 <VendorNumber>D00052</VendorNumber>
 <VendorPhone></VendorPhone>
 <VendorState>GA</VendorState>
 <VendorStreet1>PO BOX 460</VendorStreet1>
 <VendorStreet2>CIRCULATION ACCOUNT</VendorStreet2>
 <VendorVendorName>NEWSPAPERS OF WEST GEORGIA</VendorVendorName>
 <VendorZip>301170000</VendorZip>
</PORemittanceReport>

 

The xsl is 276 lines of code.  I am wondering if I should change the encoding from:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

to

<?xml version="1.0" encoding="ISO-8859-1"?>

Although I don't understand why changing the encoding  on JBoss 4.0.3SP1 on Suse or Windows (both of these platforms work as is) to JBoss 4.0.3SP1 on Redhat 2.1 would require the change in encoding to work.

 

Again, any and all help/ideas appreciated.

 

 

Thanks,

John

 

 

On 4/14/06, J.Pietschmann <[EMAIL PROTECTED]> wrote:

John Quinn wrote:
> Okay, saxon is now running under JBoss.  I still fail at the same line with
> the following error now:
...
> 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.
...
> But I don't know why it talks about null, and the only '&' in the file are
> of the following nature:

I guess the problem is in the XML source, not the XSL style sheet. I
suspect a stray (unquoted) ampersand there. The "null" is the name
SystemId of the XML input. Apparently you didn't construct the XML
input directly from a file or URL.


J.Pietschmann

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