Robert P. J. Day wrote: > > If you are using a home-grown script that is fine. However, I > suspect that > > you are actually using fop.bat or fop.sh at some point. If so, then a > > cursory examination of those scripts will show that FOP doesn't use your > > classpath at all, but builds its own. > > technically, only half true since FOP initially assigns its LOCALCLASSPATH > *from* your CLASSPATH, so certainly, if you have an archive on your > standard CLASSPATH, it will show up in the call through fop.sh.
Ouch. You are correct. My humble apologies. Thanks for setting me straight, and this triggers the following off-topic thought: <off-topic> Does anyone else think that we should move the following lines if [ -n "$CLASSPATH" ] ; then LOCALCLASSPATH=$CLASSPATH fi to a point below the remainder of the LOCALCLASSPATH building, changing the middle line to: LOCALCLASSPATH=$LOCALCLASSPATH:$CLASSPATH This would make sure that the FOP-supported libraries appear in the CLASSPATH before any user CLASSPATH entries. Probably good for Batik, maybe not so good for Xalan. Or maybe we should split the lib directory into two pieces & load the contents separately, one before and one after, so that we could load version-critical things like Batik first, then load less version-critical things like Xalan after. </off-topic> > at this point, i'm thoroughly confused as to why neither JIMI nor JAI > is successful at rendering a simple .png file. I guess I am too. Right before your "java" command that runs FOP, echo your CLASSPATH to see what is actually in there. Victor Mote --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
