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=11125>. 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=11125 Threading issue can cause NPE in DOM ------- Additional Comments From [EMAIL PROTECTED] 2002-07-24 13:10 ------- Last I checked the Xerces DOM code, like most, was minimally reentrant. Accesses to separate DOM trees could be safely conducted simultaneously, but access to a single Document and its associated nodes had to be serialized at the application level. I believe you can also get away with simultaneous reads of a single DOM tree as long as nobody attempts to alter it. This is pretty much standard operating procedure for DOM implementations. The DOM Recommendation explicitly does not guarantee reentrancy. There are some design issues which would make full reentrancy something of a pain to implement, and -- as with many data structures -- it's usually both necessary and more efficient to lock at the application level, where a multi-operation transaction can be protected as a unit, rather than trying to protect single low-level operations. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
