I understood the DTM to be immutable, a snapshot of the DOM at the time the DTM was created, are you saying this is not always the case?
I thought you can change the DOM but the DTM would not change and Xalan would only break if you tried to execute an XPath based on the changes made to the DOM. For example you add a new child to the DOM after creating the DTM and then try and execute an XPath using that child. Can you clarify a few things for me: In Statement 1 (which is from sample code I had in original email), I pass a DOM root node, so a thin DTM proxy is being created and the XPath is being executed against it? (based on your reply, this is what I'm thinking) Statement 1: XObject obj = xpath.execute(_xpathcont, _doc.getDocumentElement(), null); In Statement 2 (also from original email), I pass a DTM so no proxy is being created and the XPath is being executed against the passed DTM? Statement 2: obj = xpath.execute(_xpathcont, dtm.getDocument(), null); If I were to execute these statements one after the other do I need to worry about the XPathContext (_xpathcont)? TIA "Joseph Kesselman/CAM/Lotus" <[EMAIL PROTECTED]> on 04/26/2002 10:56:52 AM To: "Tito Burgos" <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: Getting values from DOM Document and DTM If you pass us a DOM, we wrap a thin DTM "proxy" layer around it. This means that some (not all) kinds of changes in the DOM may become visible in the DTM. We can't prevent you from changing the DOM after Xalan has started; all we can tell you is that you're likely to completely break Xalan if you try to do so.
