It should be much faster if you process more than one file in one batch compared to multiple command-line calls since the Java warm-up takes considerable time. Of course, if we included the XSL transformation in the FOP task it could be even faster. That should be looked into.
What's weird is that you got a NullPointerException because of a mistake in a path name. I think we should figure that out. What did the stack trace look like? Was it in Ant or in FOP? On 31.08.2006 22:04:31 Rick Roen wrote: > Thanks Jeremias, > > I figured it out once I had the -d switch. I had a mistake in the path on a > few of the jar files so Ant could not find them. > > I was testing this to see if it was faster than the batch file I have now. > It doesn't seem too different since it is a two step operation now of doing > the XSLT transformation from the XML file then Ant to finally get to a PDF. > > Should this be much faster? > > Rick > > -----Original Message----- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 31, 2006 11:46 AM > To: fop-users@xmlgraphics.apache.org > Subject: Re: ant task > > Hmm, can you call ant with the "-d" argument so we get the full stack > trace? "26" refers to the line number in build.xml. > > I've just rechecked the Ant trask from FOP Trunk and it works for me. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
