Class AdjacentTextNodeMergingIterator
- java.lang.Object
-
- net.sf.saxon.tree.iter.AdjacentTextNodeMergingIterator
-
- All Implemented Interfaces:
java.io.Closeable
,java.lang.AutoCloseable
,SequenceIterator
,LookaheadIterator
public class AdjacentTextNodeMergingIterator extends java.lang.Object implements LookaheadIterator, java.io.Closeable
AdjacentTextNodeMergingIterator is an iterator that eliminates zero-length text nodes and merges adjacent text nodes from the underlying iterator
-
-
Constructor Summary
Constructors Constructor Description AdjacentTextNodeMergingIterator(SequenceIterator base)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description void
close()
Close the iterator.boolean
hasNext()
Determine whether there are more items to come.Item
next()
Get the next item in the sequence.boolean
supportsHasNext()
Ask whether the hasNext() method can be called.
-
-
-
Constructor Detail
-
AdjacentTextNodeMergingIterator
public AdjacentTextNodeMergingIterator(SequenceIterator base) throws XPathException
- Throws:
XPathException
-
-
Method Detail
-
hasNext
public boolean hasNext()
Description copied from interface:LookaheadIterator
Determine whether there are more items to come. Note that this operation is stateless and it is not necessary (or usual) to call it before calling next(). It is used only when there is an explicit need to tell if we are at the last element.This method must not be called unless the result of
LookaheadIterator.supportsHasNext()
is true.- Specified by:
hasNext
in interfaceLookaheadIterator
- Returns:
- true if there are more items in the sequence
-
next
public Item 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.
-
supportsHasNext
public boolean supportsHasNext()
Description copied from interface:LookaheadIterator
Ask whether the hasNext() method can be called. This method must be called before calling hasNext(), because some iterators implement this interface, but only support look-ahead under particular circumstances (this is usually because they delegate to another iterator)- Specified by:
supportsHasNext
in interfaceLookaheadIterator
- Returns:
- true if the
LookaheadIterator.hasNext()
method is available
-
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
-
-