public interface LoopStartNode extends ScopeStartNode
NodeModelclasses to define a loop start node. The framework will take care of the details, such as finding the appropriate end node in the workflow (can be accessed after the first loop iteration using the
getLoopEndNode()method defined in the abstract
NodeModelclass) and preparing the flow object stack.
In comparison to an ordinary nodes, loop start nodes don't get their
reset() method called between loop iterations (although the
node is executed) but the output tables are cleared; secondly, if a loop
start node defines new data that needs to be kept between loop iterations
it must implement the
PortObjectHolder interface and return
the important tables in the corresponding get method (it should return
null _after_ the last iteration if the tables should not be persisted
with saving the workflow).
KNIME GmbH, Konstanz, Germany
You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, display, or in any way exploit any of the content, in whole or in part, except as otherwise expressly permitted in writing by the copyright owner or as specified in the license file distributed with this product.