Michael Glavassevich wrote on 10/14/2008 06:02:54 AM:
> In Xerces I'm pretty sure a cloned Document is completely disconnected from > the original with possibly > the exception of user data your application may have copied over. It should > generally be safe to use it in > a different thread than the original Document. With one exception: In Xerces event listener Management is done upon a partially static data structure and thus registering or unregistering event listeners upon otherwise completely disconnected documents concurrently is subject to race conditions possibly causing corrupt event listener entries as I tried to discuss three weeks ago[1]. If anyone is interested, I have a fix for this which is already working fine in our local application. But before I can place a report in jira I need feedback about the related issue I raised two weeks ago because it will influence how it should be done: Are event listener entries supposed to be serializable or it is sufficient to keep them transient only? Because of the above mentioned static LCount data structure, event listener entries are already not properly serializable and thus broken in Xerces and need a fix anyhow. Best Regards, Ludger Bünger [1] http://mail-archives.apache.org/mod_mbox/xerces-j-dev/200809.mbox/[EMAIL PROTECTED]
