FOP problems with Unix
Hi all, I have a strange problem. Under Windows, everything works ok, the FOP serializer creates a PDF file. But under Unix, some files are converted ok and some aren't. The FOP xml file created by the pipeline is the same. I've tried to convert it to pdf by invoking directly FOP through a command line and it works. So it must be something related to the interface between FOP and Cocoon. In addition, I don't get any error message in the logs. I'm using Cocoon 2.0.4 Any help would be greatly appreciated. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP problems with Unix
I've had this problem many times: you need an X windows display (the DISPLAY environment variable) set to a viable display (like localhost:0.0) first OR use the headless Java stuff in JDK 1.4 (see the Cocoon install notes or Wiki). -- jack John R. Callahan, Ph.D. CTO [EMAIL PROTECTED] Sphere Software Corporation - Original Message - From: Carmona Perez, David [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 10:40 AM Subject: FOP problems with Unix Hi all, I have a strange problem. Under Windows, everything works ok, the FOP serializer creates a PDF file. But under Unix, some files are converted ok and some aren't. The FOP xml file created by the pipeline is the same. I've tried to convert it to pdf by invoking directly FOP through a command line and it works. So it must be something related to the interface between FOP and Cocoon. In addition, I don't get any error message in the logs. I'm using Cocoon 2.0.4 Any help would be greatly appreciated. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FOP problems with Unix
Thanks, Maybe this is the cause, as my Unix system has no X windows. But I wonder why some files are processed ok and others don't, or why can I do it from the command line. David -Mensaje original- De: John R. Callahan [mailto:[EMAIL PROTECTED] Enviado el: miƩrcoles, 18 de junio de 2003 17:40 Para: [EMAIL PROTECTED] Asunto: Re: FOP problems with Unix I've had this problem many times: you need an X windows display (the DISPLAY environment variable) set to a viable display (like localhost:0.0) first OR use the headless Java stuff in JDK 1.4 (see the Cocoon install notes or Wiki). -- jack John R. Callahan, Ph.D. CTO [EMAIL PROTECTED] Sphere Software Corporation - Original Message - From: Carmona Perez, David [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 10:40 AM Subject: FOP problems with Unix Hi all, I have a strange problem. Under Windows, everything works ok, the FOP serializer creates a PDF file. But under Unix, some files are converted ok and some aren't. The FOP xml file created by the pipeline is the same. I've tried to convert it to pdf by invoking directly FOP through a command line and it works. So it must be something related to the interface between FOP and Cocoon. In addition, I don't get any error message in the logs. I'm using Cocoon 2.0.4 Any help would be greatly appreciated. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FOP problems with Unix
On Wed, 2003-06-18 at 11:00, Carmona Perez, David wrote: Thanks, Maybe this is the cause, as my Unix system has no X windows. But I wonder why some files are processed ok and others don't, or why can I do it from the command line. i'm not sure if you're running into the same problem i was. in my case, i solved it by removing the batik-xx.jar fop-xx.jar that came with cocoon and downloaded the latest binaries from FOP ( i actually did if from source but it would have the same effect). then copied these files into the cocoon/WEB-INF/lib directory: batik-awt-util.jarbatik-dom.jar batik-parser.jar batik-svggen.jar batik-util.jar batik-bridge.jar batik-ext.jar batik-script.jar batik-swing.jar batik-xml.jar batik-css.jar batik-gvt.jar batik-svg-dom.jar batik-transcoder.jar and of course the fop.jar from the FOP distribution. the reason for this is (i think) is api mismatch between fop and batik. especially in the 'inline-foreign-object: svg' part. anoop [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP problems with Unix
Carmona Perez, David wrote: But I wonder why some files are processed ok and others don't, or why can I do it from the command line. Those without SVG (inline or external images) should be ok. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]