Hi Alexis
Thanks for the patch! I'll look at it shortly. Would you mind attaching
it to the Bugzilla issue?
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360
That way it's clearer that you donate the changes to the ASF and
everything concerning this problem is in one place. Thanks!
On 02.
Jeremias, thanks for the clarification about the FopFactory.
I had a look at your old commit at
http://svn.apache.org/viewvc?view=revision&revision=724163
The current situation in trunk is that in
PDFImageHandlerSVG.handleImage() the SVG document is not cloned but in
other places it is. Exampl
Peter could be right. And there I thought I had this under control. But
with so many open Bugzilla issues, things get lost quickly. I've seen
multi-threading issues inside Batik myself in a production system and
haven't been able to put my finger on it since I though I had this fixed,
but it could
Hi Peter,
Thanks for pointing this out. It differs in that the instance of
FOUserAgent was shared, but other than this, it's exactly the same case.
Finally, this leads to
https://issues.apache.org/bugzilla/show_bug.cgi?id=46360
which is still open.
As I read from the thread, this is a compl
Alexis,
This reminds me of something similar I ran into a while ago. I can't remember
the details nor how I eventually got around this and/or whether you run into
the same but the (weird) behavior you describe does look very similar.
See
http://old.nabble.com/Batik-exception-when-using-fop-wit
Hello,
The javadoc and the class name suggest that FopFactory should be
thread-safe although this is not explicitly written. If this is not
thread-safe then please ignore what follows.
I am using FOP 1.0 to produce PDF documents concurrently from FOP
intermediate format. The PDF documents sh
