[kaffe] CVS kaffe (dalibor): Small fix for FOP

[Dalibor Topic]

Arnaud Vandyck wrote:
> Kaffe CVS <cvs-commits at kaffe.org> writes:
> 
> 
>>PatchSet 4197 
>>Date: 2003/12/04 15:07:14
>>Author: dalibor
>>Branch: HEAD
>>Tag: (none) 
>>Log:
>>Small fix for FOP
> 
> 
> Dalibor,
> 
> Can you put images in pdf files without using 'jimi.jar'?

I've just used fop 0.20.5' fop.sh as it was without downloading extra 
files. I couldn't find a jimi.jar in lib/ so I doubt it's included.

I've only looked at SVG images for real, and those atm due to two 
things: the DirectColorModel bug, and a lack of Java2D.

Running fop on examples/fo/basic/images.fo gives:

../../../fop.sh -d images.fo images.fo.pdf
[DEBUG] Input mode:
[DEBUG] FO
[DEBUG] fo input file: images.fo
[DEBUG] Output mode:
[DEBUG] pdf
[DEBUG] output file: images.fo.pdf
[DEBUG] OPTIONS
[DEBUG] no user configuration file is used [default]
[DEBUG] debug mode on
[DEBUG] dump configuration
[DEBUG] quiet mode on
[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
[INFO] base directory: file:/tmp/topic/fop/fop-0.20.5/examples/fo/basic/
[INFO] FOP 0.20.5
[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
[INFO] building formatting object tree
[INFO] setting up fonts
[INFO] [1]
java.lang.NoClassDefFoundError: 
com/sun/media/jai/codec/FileCacheSeekableStream
    at org.apache.fop.image.TiffImage.loadImage (TiffImage.java:92)
    at org.apache.fop.image.AbstractFopImage.getWidth 
(AbstractFopImage.java:207)
    at org.apache.fop.fo.flow.ExternalGraphic.layout 
(ExternalGraphic.java:192)
    at org.apache.fop.fo.flow.Block.layout (Block.java:257)
    at org.apache.fop.fo.flow.Block.layout (Block.java:257)
    at org.apache.fop.fo.flow.AbstractFlow.layout (AbstractFlow.java:154)
    at org.apache.fop.fo.flow.AbstractFlow.layout (AbstractFlow.java:110)
    at org.apache.fop.fo.pagination.PageSequence.makePage 
(PageSequence.java:400)
    at org.apache.fop.fo.pagination.PageSequence.format 
(PageSequence.java:338)
    at org.apache.fop.apps.StreamRenderer.render (StreamRenderer.java:262)
    at org.apache.fop.fo.FOTreeBuilder.endElement (FOTreeBuilder.java:223)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement (source 
file unknown)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement 
(source file unknown)
    at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch 
(source file unknown)
    at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument 
(source file unknown)
    at org.apache.xerces.parsers.DTDConfiguration.parse (source file 
unknown)
    at org.apache.xerces.parsers.DTDConfiguration.parse (source file 
unknown)
    at org.apache.xerces.parsers.XMLParser.parse (source file unknown)
    at org.apache.xerces.parsers.AbstractSAXParser.parse (source file 
unknown)
    at org.apache.fop.apps.Driver.render (Driver.java:498)
    at org.apache.fop.apps.CommandLineStarter.run 
(CommandLineStarter.java:106)
    at org.apache.fop.apps.Fop.main (Fop.java:62)

Judging by http://xml.apache.org/fop/graphics.html , FOP 0.20.5 should 
have native TIFF support. Unfortuantely, for some reason, it insists on 
using JAI anyway.

Actually, judging by 
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/org/apache/fop/image/Attic/TiffImage.java?annotate=1.1.2.2
using JAI was hardcoded on this branch. The HEAD version of FOP doesn't 
have that file anymore anyway, so it may work better/without JAI/JIMI 
with the CVS HEAD of FOP. I haven't tried building that, so I can't 
really tell.

But it would be nice if someone would get FOP developers interested in 
getting it to work with a free runtime wrt. to image handling.

cheers,
dalibor topic