[EMAIL PROTECTED] wrote:
ok, I run the same thing with PDFRenderer, and I found no problems there.
This means that the multithreading issue is either within
a) AWTRenderer
b) TIFFRenderer (subclass of AWTRenderer)
c) pja X-Server emulation.
Since the issue is, that fontsize-changes from one Renderer influence
another Renderer, I suspect the mistake to be in a) or c). AFAIK FOP paints
the characters to the InMemory-Image in these classes. Is this correct?
Probably not. Renderers in general are not MT safe, but I found
critical stuff only in the PDF renderer (static variables holding
a StringBuffer which is filled an reset in an unsync'd routine
in pdf/PDFCIDSystemInfo.java:21 and PDFWArray.java:99).
There are more unprotected static variables but they seem mostly
be changed by configuration, so if you load your configuration
file only once, it shouldn't be that bad.
Has anyone used AWTRenderer in a mutlithreaded environment?
Well, the AWT renderer bears the comment attributed to Mark
Lillywhite:
"... This class could also do with a general audit,
and I suspect it's not swing-thread-safe either."
However, the class was designed for use in a stand-alone viewer,
not for general purpose and multi-threaded environments. I still
didn't find much unprotected static data, however, you might want
to inspect the sourtce yourself.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
