Hi all,

I’m getting bad output from my fo2pdf serialization (I’ve pasted a sample below).  Based on an old thread (http://www.mail-archive.com/[EMAIL PROTECTED]/msg12064.html) I gather that the problem is that the mime type is not getting set for some reason so the browser is outputting raw pdf code.  My serializer setup is below, and is setting the mime type, so I am stumped as to what the problem is.  Any hints would be much appreciated.

 

Thanks,

David

 

 

Here’s the serializer setup:

    <map:serializer name="fo2pdf"

                      src="org.apache.cocoon.serialization.FOPSerializer"

                      mime-type="application/pdf">

        <user-config>C:/java/hibapp2/fop-fonts/config.xml</user-config>

    </map:serializer>

 

And the pipeline:

    <map:match pattern="*.pdf">

        <map:generate type="file" src="invoice.xml" />

        <map:transform type="xalan" src="test.xsl" />

        <map:serialize type="fo2pdf" />

    </map:match>

 

And here’s the garbage output I get:

%PDF-1.3 %ª«¬­ 4 0 obj << /Type /Info /Producer (FOP 0.20.5) >> endobj 5 0 obj << /Length 90 /Filter [ /ASCII85Decode /FlateDecode ] >> stream Garg^iR2p+<%p/W1Je?Kj"^U3a]o#Wl!/rM#!ck#?u?;c1G^u;1UJi5#g$)&egO*A0%!XS<=&-SEXgt/!5Om1.0~> endstream endobj 6 0 obj << /Type /Page /Parent 1 0 R /MediaBox [ 0 0 612 792 ] /Resources 3 0 R /Contents 5 0 R >> endobj 7 0 obj << /Type /Font /Subtype /Type1 /Name /F1 /BaseFont /Helvetica /Encoding /WinAnsiEncoding >> endobj 1 0 obj << /Type /Pages /Count 1 /Kids [6 0 R ] >> endobj 2 0 obj << /Type /Catalog /Pages 1 0 R >> endobj 3 0 obj << /Font << /F1 7 0 R >> /ProcSet [ /PDF /ImageC /Text ] >> endobj xref 0 8 0000000000 65535 f 0000000464 00000 n 0000000522 00000 n 0000000572 00000 n 0000000015 00000 n 0000000071 00000 n 0000000251 00000 n 0000000357 00000 n trailer << /Size 8 /Root 2 0 R /Info 4 0 R >> startxref 650 %%EOF


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.515 / Virus Database: 313 - Release Date: 9/1/2003

Reply via email to