> I suppose the main question comes down to "what >types of changes to the DOM would constitute > invalidation of the XPathContext"? You may want to look at the experimental DOM2DTM2 class. This won't work with all DOMs -- if I remember correctly it requires the ability to hang "user data" off the side of a DOM node -- and it may be less performant than the standard DOM2DTM solution in some cases. And it may have bugs; we set it aside only partly completed... But it was developed specifically to address those cases where the DOM may be altered between XPath invocations. We've had several other ideas which might address this (XDM, for example, ought to be a more general solution).... But I'm currently three levels deep in recursive "have to make this work to support that", so I haven't been able to pursue them. ______________________________________ Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more. "The world changed profoundly and unpredictably the day Tim Berners Lee got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
