Hi Prashant,
That won't work either. The NodeList caches are managed by a pooling
mechanism (on the Document node) which is also not thread-safe. You need a
lock on the entire DOM instance.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@xxxxxxxxxx
E-mail: mrglavas@xxxxxxxxxx
Prashant Reddy <prashant@xxxxxxxxxxx> wrote on 07/27/2007 03:44:13 AM:
> What about writing a utility class that wraps the Xerces NodeList
> implementations with your own NodeList that will behave according to
> your expectations even in concurrent read access. Let your application's
> code use this object instead of using the one xerces returns.
|
