Chris Simmons <c...@corefiling.com> wrote on 06/08/2011 04:05:51 AM: > On 08/06/11 05:06, Michael Glavassevich wrote: > > > > Hi John, > > > > None of Xerces' DOM implementations are thread-safe, even the > > non-deferred ones. This is true even for read operations. In > > particular, the implementation of the NodeList methods (i.e. item() > > and getLength()) are not thread-safe. These methods do some internal > > writes to a cache which are necessary for good performance. There's a > > longer explanation in the JIRA issue you found. > > > > Thanks. > > > > Michael Glavassevich > > XML Parser Development > > IBM Toronto Lab > > E-mail: mrgla...@ca.ibm.com > > E-mail: mrgla...@apache.org > > > Given that this keeps coming up, wouldn't it be prudent to fix this > issue or have a separate DOM implementation that's read thread-safe? > > Would it really be that difficult?
More time has passed but the answer [1] is still the same. Plus if you're expecting your code to work [2] with any DOM implementation (not just a specific one you've locked yourself into) you need to synchronize anyway. > Chris Simmons. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-users-h...@xerces.apache.org Thanks. [1] http://markmail.org/message/s7aniecyk4kwckdg [2] http://markmail.org/message/jserv2iaeivutuuk Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org
