Re: CachedXPathAPI needs to be discarded when new Node is created, or only if Document tree is changed?

That should be safe.

______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
  -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (
http://www.ovff.org/pegasus/songs/threes-rev-11.html)

"Gary Hirschhorn" <[email protected]> wrote on 04/22/2009 11:00:40 AM:

> "Gary Hirschhorn" <[email protected]> 
> 04/22/2009 11:00 AM
> 
> To
> 
> <[email protected]>
> 
> cc
> 
> Subject
> 
> CachedXPathAPI needs to be discarded when new Node is created, or 
> only if Document tree is changed?
> 
> Suppose we are using a CachedXPathAPI object.  We then use 
> Node.createClone() or Document.newElement() to create a new Element 
> that is owned by the Document, but has no parent and is not in the 
> Document tree.  Is the CachedXPathAPI object we are using still 
> valid?  Or is the Document now considered "changed", and we need to 
> create a new CachedXPathAPI object?
> 
> Thanks, 
> Gary
>