DO NOT REPLY [Bug 13039] - Xalan's DOMSource is not thread-safe

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13039>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13039

Xalan's DOMSource is not thread-safe





------- Additional Comments From keshlam@us.ibm.com  2002-09-26 17:22 -------
DOMs are not promised to be threadsafe. They _usually_ are under read, but a 
single DOM really should not be used as the source for simultaneous 
transformations, and nothing else should be done with that DOM while 
transformation is in progress.

For now, I'd suggest you serialize the transformation runs which are accessing a 
single DOM at a higher level, or -- as noted -- use a StreamSource or SAXSource. 
Note that DOMSource has some performance and memory-size issues at this time, so 
if you're working with an unchanging document it's very unclear that processing 
from a DOM is gaining you anything.

I'm working on a major revision to DOM2DTM. At this time it isn't intended to be 
threadsafe either, but it may be easier to make threadsafe if folks are willing 
to pay the performance penalty for that protection. I'm inclined to table this 
issue until we see whether that leads us in a useful direction.