Hmm, maybe because we use JBoss + Tomcat + Cocoon. Do you know what changed between Fop 0.20.3 and 0.20.4, that prevents my old stuff from working? Or is it deep Fop interna?
There were two changes: the switch from using Xerces native to JAXP for creating the XML parser for reading the config file and feeding the metrics-file name directly to the InputSource constructor instead of creating a File first (which means it is interpreted as URL rather than as filename, making Windows path names like "C:\foo" problematic).
The new 0.20.5 release has some improvements, in particular you can supply a baseURL for images and a fontBaseURL for font related files. Documentation may be a bit sparse, you might have to blackmail Jeremias to get it :-)
If you (or anybody else) are interested into looking at ideas for the FOP API redesign, look at http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAvalonization Also, it's a Wiki, you *can* edit it to bring in your ideas.
J.Pietschmann
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
