DO NOT REPLY [Bug 27454] - Traversing the DOM throws NullPointerException

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

http://issues.apache.org/bugzilla/show_bug.cgi?id=27454

Traversing the DOM throws NullPointerException





------- Additional Comments From mrglavas@xxxxxxxxxx  2004-03-19 19:10 -------
We clearly state in our documentation that Xerces' DOM implementation is not 
thread-safe [1].  The DOM specification doesn't require that implementations be 
thread-safe and indeed some of the ones out there are not, including the ones 
in Xerces.

Even if the Xerces' DOM implementations were thread-safe, code written to the 
DOM interfaces is supposed to be interoperable, meaning users should be able to 
swap between DOM compliant parsers which may also not have a thread-safe DOM 
implementation. So as long as you've coded to what the DOM spec says and not 
assume things like thread-safety and that instanceof checks on nodes are 
equivalent to calling getNodeType() you should be seeing the same behaviour 
from any compliant parser.

It's up to the application to synchronize it's access to an instance of the DOM 
even if it's only reading it.

[1] http://xml.apache.org/xerces2-j/faq-dom.html#faq-1