Hi, *Xerces' DOM is not thread-safe and is not required to be. If you're going to be sharing an instance of the DOM across threads you need to synchronize your access to it.
See previous threads on this topic in the mailing list archives [1].* Thanks for the reply. I know that DOM access is not thread safe. But i would like to get confirmed whether these issues are possible because of concurrent access. - Some child nodes of an element node are not coming in getChildNodes - I am getting different child nodes of an element node. These child nodes are not in no way related to the given element node. Thanks Prasanna On Fri, Aug 13, 2010 at 6:01 PM, Prasanna <pra...@gmail.com> wrote: > Hi, > > I just have few doubts with respect to concurrent access of elements. I am > caching the elements and threads in the system will share these elements > These threads will do node.getChildNodes & nodeList.item etc. > > I am getting the following issues. Can you please confirm whether these > issues are related to concurrent access. Version i am using is 2.6.2 > > - Some child nodes of an element node are not coming in getChildNodes > - I am getting different child nodes of an element node. These child > nodes are not in no way related to the given element node. > > > I know, that the xerces is not designed for concurrent access. But i would > like to get confirmed whether the above are related to concurrent access. > > Thanks > Prasanna >
