This is not a huge matter. More on the line of an annoyance. And I
may need to take this question to a java list rather than this list.
If so, just point me in the right direction.
At any rate, I have an XSLT stylesheet that produces 50+ separate fo
documents. I then run the shell script be
If you are doing that much formatting, you may really want to check
out using ant for your build process, especially if doing multiple
output formats. I use this on Mac OS X and have no problem with
background running or anything else. My rule for PDF formatting is just:
It
Use 'nice' to run it. Alter the script so that the fop execution looks
like:
nice /Applications/fop-0.94/fop -fo $foo -pdf ../pdf_files/$state.pdf
You can check the man page for nice for more info.
Steve
On Thu, 3 Jan 2008, Terry Ofner wrote:
This is not a huge matter. More on the line of
nice does not seem to change the outcome. It only changes the
priority of the process. When it runs, it still places fop in the
foreground. Here is what I have tried:
nice /Applications/fop-0.94/fop -fo $foo -pdf ../pdf_files/$state.pdf &
nice -n 20 /Applications/fop-0.94/fop -fo $foo -pdf ..
Actually that probably won't do what you want. Adding -
Djava.awt.headless=true to the vm arguments in the fop script probably
will work.
On Jan 3, 2008, at 8:36 AM, Steve Quirk <[EMAIL PROTECTED]> wrote:
Use 'nice' to run it. Alter the script so that the fop execution
looks like:
nic
James,
Your suggestion works. I have no idea where the vm arguments are in
the fop script. So I changed my script to invoke the jar directly,
adding the headless argument. I had to move all the jar files in fop/
lib to the build directory to get this to work:
java -Djava.awt.headless=true
I had looked at the fop script I had and saw it there. I wasn't sure that
I had made the change or not. In any case, if it's helpful, it should
look like:
fop_exec_command="exec \"$JAVACMD\" ${ENDORSED} -Djava.awt.headless=true
$LOGCHOICE $LOGLEVEL -classpath \"$LOCALCLASSPATH\" $FOP_OPTS
Steve,
Yep. That works too. On 0.94 the fop_exec_command is near the bottom
of the fop script and looks like this:
fop_exec_command="exec \"$JAVACMD\" -Djava.awt.headless=true
$LOGCHOICE $LOGLEVEL -classpath \"$LOCALCLASSPATH\" $FOP_OPTS
org.apache.fop.cli.Main $fop_exec_args"
Note: The
Thanks for the ant tip Eric. The following build.xml does the trick
for the fop part of my process. I notice that the process is much
faster: 1 minute 45 seconds for 52 pdf documents. Before it was
taking anywhere from 8 to 11 minutes.
Here is my build.xml file:
Terry Ofner wrote:
I have not studied how to include the XSLT transformation. Here is how
it would go:
source XML document xslt transform via saxon (xslt 2.0) ---> 50+ .fo
documents ---fop--->50+ pdf documents.
The xslt automatically produces the 50 fo docs via
. Would all this go into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have not studied how to include the XSLT transformation. Here is
how it would go:
source XML document xslt transform via saxon (xslt 2.0) ---> 50
+ .fo documents ---fop--->50+ pdf documents.
The xslt automatically produces the 50 fo do
A little over a month ago I switched from running fop using a shell
script to using ant, as per Eric Vought's suggestion copied below.
Today I ran into a strange file-naming issue.
I am processing multiple files based on state and grade level. The
PDFs will eventually end up on a Web site.
12 matches
Mail list logo
