Your solution is likely a bit simpler than mine. Here's the issue I had. I'm not calling fop from a command line. I'm actually creating a java object using the classes within another language which has it's own classpath, so I got rid of FOP's classpath. I just downloaded the source and removed the classpath from the manifest.mf file by editing it out of the build.xml and running the ant build in Eclipse. Then I looked in every jar referenced in the FOP classpath for other classpath statements in manifest.mf files. I had to edit out and recompile at least the xalan. I think that was the only other one. I added all the required jars to the classpath of the language (http://www.basis.com/products/lanint/bbj/index.html) and replaced the commons-logging there with the newer one.
I think you just need to download the source and remove the commons-logging from the FOP project lib folder, put the 1-1-1 jar in there and run the ant build. You may need to modify build.xml. Some references in the build file were looking for specific jars and some used wildcards to pick up whatever version is in the folder. The Trunk might have a similar issue but of course it doesn't have a binary download to begin with. -----Original Message----- From: Jayant Ghagre [mailto:[email protected]] Sent: Tuesday, June 29, 2010 10:02 AM To: [email protected] Subject: RE: FOP 0.95 as Database Resident Objects in Oracle 11g Release 1 Eric, Thanks for the reply. I did check the manifest file in FOP.jar and it matches with the list of files, I have specified in the loadjava option. I'll download the commons-logging-1.1.1 and try again. But in such case, do I need to compile FOP because FOP.jar would refer to commons-logging-1.0.4.jar, isn't it? Oracle documentation recommends loading classes/jars from bottom of the hierarchy. How can I get the complete dependency tree for FOP.Jar and it's dependencies? Manifest in each jar is my only option? Thanks for your help. Regards, Jayant --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
