Hi, -xsl and -xml command line parameters are there for convenience. FOP delegates XSLT transformation to Xalan before do its own job: render pdf (or whatever supported format).
You can do the XSLT transformation by yourself, using whatever XSLT processor you want, and feed FOP with resulting XSL-FO. That can be done a batch processing. So, Xalan dependencies (and associated Xerces) can be removed from FOP bundle. 2014-05-14 10:38 GMT+02:00 Peter <p.kullm...@arenae.ch>: > Actually, we are using -xsl and -xml as input. > > > Glenn Adams-2 wrote >> Personally, I support removing all XSLT functions from FOP, but I'm afraid >> that would cause many users to find it less useful. I think it was a >> serious architectural error to combine those functions in the first place, >> but that horse left the gate long ago. >> >> >> On Tue, May 13, 2014 at 4:18 AM, Peter < > >> p.kullmann@ > >> > wrote: >> >>> We had some performance problems with fop and began to investigate. For a >>> specific example document of about 400 pages fop took about 55 seconds on >>> a >>> server at a client. The same process was much faster in our own setting >>> (taking about 11 seconds). What we found out is the following: >>> >>> - fop from the distribution (either 1.1 release or 1.2 snapshot) takes 55 >>> seconds >>> - fop from the suse package takes only 11 seconds >>> >>> The two configurations differ in the jars: The suse config does not >>> include >>> xercesImpl, xalan and serializer >>> >>> We are running >>> java version "1.7.0_40" >>> OpenJDK Runtime Environment (IcedTea 2.4.1) (suse-8.18.1-x86_64) >>> OpenJDK 64-Bit Server VM (build 24.0-b50, mixed mode) >>> >>> So, removing these three libraries drastically improved performance for >>> us. >>> >>> Can someone explain why this is so? Can I safely drop these jars? -- pascal --------------------------------------------------------------------- To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
