Yes, at the moment, this only works when interfacing through Java. The
ability to configure which events cause what for the command-line
interface has simply not been implemented, yet. I very rarely run FOP
from the shell. For me personally, FOP is primarily a software library
to integrate in
Are you saying I need to create my own fop runner to do such a thing? It
can't be done using the regular fop script?
Seems like an unfortunate design choice. Or maybe I'm missing something...
I always thought the fop script was the primary method of using fop, but
perhaps I'm wrong.
/Oskar
See http://xmlgraphics.apache.org/fop/2.1/events.html for an example of
exactly that.
HTH
Jeremias Maerki
On 12.05.2016 23:12:22 Oskar Berggren wrote:
> Hi,
>
>
> Sometimes a document will reference an image that FOP is unable to find. With
> FOP 2.0, it will print a SEVERE log and then
Hi,
Sometimes a document will reference an image that FOP is unable to find.
With FOP 2.0, it will print a SEVERE log and then continue processing the
file, eventually exiting with a regular zero exit code.
Because there may be a significant amount of other logs, and because this
FOP was invoked
