On 07.12.2008 13:07:43 Peter Coppens wrote: > Ok....I'll be more careful in my wordings. In this specific case the > problems seems to originate from the fact that the Parser object, attached > to the DOM is not thread safe while it is being used across threads. > > Unfortunately I have no clue what is the best way to fix the issue.
Me, neither. That's why I'm asking all these questions. > Serializing the svg fop rendering on the dom fixed it in this case but that > is clearly a sledge hammer approach. Yeah, that's a short-term work-around I'm not comfortable with. > I don't know how the rest of the stylesheet can influence the result of the > rendering...so I guess that caching the rendered SVG document iso the dom is > not an option? Do you mean caching the GVT tree? I'm not sure if that's feasible. But if it is, it might actually a better way of caching a static SVG image before it is painted. But this might actually be difficult, since we need to register different bridges for different output formats meaning that the GVT tree will look differently depending on the output format and configuration used. This feels more and more like an occasion to fundamentally revisit how we handle SVG in FOP. Maybe we actually did the thing wrong the whole time. <snip/> Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
