You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Jeff Sexton <se...@odscompanies.com> on 2004/12/03 19:07:07 UTC

2.0.4 to 2.1.4 fop problems

A part of our application presents XML as PDF and has been working with Cocoon 
2.0.4.

Migrating everything to 2.1.4 the PDF requests throw an exception.

org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
java.lang.RuntimeException: java.lang.ClassCastException: 
org.apache.fop.fo.flow.Block

I've confirmed that the identical XSL and XML source are correctly converted to 
PDF by Cocoon 2.0.4.  fop and batik where enabled in the build, and I've 
adjusted the Tomcat server's endorsed lib property to point to Cocoon's.  No luck.

Any ideas?  Thanks.

-- 
The ODS Companies
Jeff Sexton
Information Services
(503) 228-6554   x1026
http://www.odscompanies.com

This message is intended for the sole use of the individual and entity
to whom it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are
not the intended addressee, nor authorized to receive for the intended
addressee, you are hereby notified that you may not use, copy, disclose
or distribute to anyone the message or any information contained in the
message. If you have received this message in error, please immediately
advise the sender by reply email and delete the message.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: 2.0.4 to 2.1.4 fop problems

Posted by Jeff Sexton <se...@odscompanies.com>.
Found it!  Thanks

J.Pietschmann wrote:
> Jeff Sexton wrote:
> 
>> Migrating everything to 2.1.4 the PDF requests throw an exception.
>>
>> org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
>> java.lang.RuntimeException: java.lang.ClassCastException: 
>> org.apache.fop.fo.flow.Block
> 
> 
> This indicates that you have an incorrectly placed block somewhere,
> which was tolerated by the slightly older FOP included in Cocoon 2.0.4.
> 
> Get the XML and XSLT, run Xalan in order to produce a FO file, get
> the latest FOP distribution, and run the FO file through the FOP
> command line, using the -d flag. You'll get a stack trace with
> more information about the problem, and with some luck an indication
> where the problem is in the FO file.
> 
> J.Pietschmann


-- 
The ODS Companies
Jeff Sexton
Information Services
(503) 228-6554   x1026
http://www.odscompanies.com

This message is intended for the sole use of the individual and entity
to whom it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are
not the intended addressee, nor authorized to receive for the intended
addressee, you are hereby notified that you may not use, copy, disclose
or distribute to anyone the message or any information contained in the
message. If you have received this message in error, please immediately
advise the sender by reply email and delete the message.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: 2.0.4 to 2.1.4 fop problems

Posted by "J.Pietschmann" <j3...@yahoo.de>.
Jeff Sexton wrote:
> Migrating everything to 2.1.4 the PDF requests throw an exception.
> 
> org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
> java.lang.RuntimeException: java.lang.ClassCastException: 
> org.apache.fop.fo.flow.Block

This indicates that you have an incorrectly placed block somewhere,
which was tolerated by the slightly older FOP included in Cocoon 2.0.4.

Get the XML and XSLT, run Xalan in order to produce a FO file, get
the latest FOP distribution, and run the FO file through the FOP
command line, using the -d flag. You'll get a stack trace with
more information about the problem, and with some luck an indication
where the problem is in the FO file.

J.Pietschmann

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org