(Element) Document.getDocumentElement().cloneNode(true);
This actually didn't eliminate all my exceptions at first, but once I synchronized the above operation , it appeared to fix my exception problems. I haven't seen the exception yet and have rerun the test many times, so that problem is probably fixed (or it might be that the synchronize changed the timing enough to make it harder to get to).
I still haven't heard; should Node/NodeList be safe to access currently for read only kind of operations?
Edward L. Knoll wrote:
We have a custom ContentHandler in a SAX processing chain which we use to filter for nodes we wish to pass on. The filter is defined via a XML file which we read into a NodeList. Since the filter definition is static and we are only reading the NodeList, we set the filter up to be shared between instances of the associated ContentHandler.
We are (intermittently) getting exceptions within the NodeList.getLength() method. I don't know if our expectations are inappropriate or if there is some problem buried within this NodeList method/class.
If it is a problem, I can't supply source/data (company proprietary policies), so I hope that's enough to go on.
I will be working on an alternate implementation, so am not looking for resolution (although suggestions are welcome, if timely :).
--
Edward L. Knoll Phone (FedEx) : (719)484-2717
e-mail (FedEx) : [EMAIL PROTECTED]
e-mail (personal) : [EMAIL PROTECTED]--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
