Class IntersectionIterator
- java.lang.Object
-
- net.sf.saxon.expr.IntersectionIterator
-
- All Implemented Interfaces:
java.io.Closeable
,java.lang.AutoCloseable
,SequenceIterator
public class IntersectionIterator extends java.lang.Object implements SequenceIterator
An enumeration representing a nodeset that is an intersection of two other NodeSets. This implements the XPath 2.0 operator "intersect".
-
-
Constructor Summary
Constructors Constructor Description IntersectionIterator(SequenceIterator p1, SequenceIterator p2, java.util.Comparator<? super NodeInfo> comparer)
Form an enumeration of the intersection of the nodes in two nodesets
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description void
close()
Close the iterator.NodeInfo
next()
Get the next item in the sequence.
-
-
-
Constructor Detail
-
IntersectionIterator
public IntersectionIterator(SequenceIterator p1, SequenceIterator p2, java.util.Comparator<? super NodeInfo> comparer) throws XPathException
Form an enumeration of the intersection of the nodes in two nodesets- Parameters:
p1
- the first operand: must be in document orderp2
- the second operand: must be in document ordercomparer
- Comparer to be used for putting nodes in document order- Throws:
XPathException
- if an error occurs, for example reading from the input sequence
-
-
Method Detail
-
next
public NodeInfo next()
Description copied from interface:SequenceIterator
Get the next item in the sequence. This method changes the state of the iterator.- Specified by:
next
in interfaceSequenceIterator
- Returns:
- the next item, or null if there are no more items. Once a call on next() has returned null, no further calls should be made. The preferred action for an iterator if subsequent calls on next() are made is to return null again, and all implementations within Saxon follow this rule.
-
close
public void close()
Description copied from interface:SequenceIterator
Close the iterator. This indicates to the supplier of the data that the client does not require any more items to be delivered by the iterator. This may enable the supplier to release resources. After calling close(), no further calls on the iterator should be made; if further calls are made, the effect of such calls is undefined.For example, the iterator returned by the unparsed-text-lines() function has a close() method that causes the underlying input stream to be closed, whether or not the file has been read to completion.
Closing an iterator is important when the data is being "pushed" in another thread. Closing the iterator terminates that thread and means that it needs to do no additional work. Indeed, failing to close the iterator may cause the push thread to hang waiting for the buffer to be emptied.
Closing an iterator is not necessary if the iterator is read to completion: if a call on
SequenceIterator.next()
returns null, the iterator will be closed automatically. An explicit call onSequenceIterator.close()
is needed only when iteration is abandoned prematurely.It is not possible to guarantee that an iterator that is not read to completion or will be closed. For example, if a lazy-evaluated variable
$var
is passed to a user-written function, the function may access$var[1]
only; we have no way of knowing whether further items will be read. For this reason, anySequenceIterator
that holds resources which need to be closed should use theCleaner
mechanism. TheConfiguration
holds aCleaner
, and resources held by aSequenceIterator
should be registered with theCleaner
; if theSequenceIterator
is then garbage-collected without being closed, theCleaner
will ensure that the underlying resources are closed. (An example of aSequenceIterator
that uses this mechanism is theUnparsedTextIterator
).- Specified by:
close
in interfacejava.lang.AutoCloseable
- Specified by:
close
in interfacejava.io.Closeable
- Specified by:
close
in interfaceSequenceIterator
-
-