final class CreateTempDirectoryNodeModel extends NodeModel
|Constructor and Description|
|Modifier and Type||Method and Description|
This function is called whenever the derived model should re-configure and generate the expected output specs.
Configure method for general port types.
Execute method for general port types.
Load internals into the derived
Sets new settings from the passed object in the model.
Called by the framework when the node is disposed, for instance if the workflow is closed or the node is deleted by the user.
Override this function in the derived model and reset your
Save internals of the derived
Adds to the given
Validates the settings in the passed
addWarningListener, computeFinalOutputSpecs, continueLoop, createInitialStreamableOperatorInternals, createMergeOperator, createStreamableOperator, execute, finishStreamableExecution, getAvailableFlowVariables, getAvailableInputFlowVariables, getCredentialsProvider, getInHiLiteHandler, getInPortType, getInputPortRoles, getInteractiveNodeView, getLogger, getLoopEndNode, getLoopStartNode, getNrInPorts, getNrOutPorts, getOutHiLiteHandler, getOutPortType, getOutputPortRoles, getWarningMessage, iterate, notifyViews, notifyWarningListeners, peekFlowVariableDouble, peekFlowVariableInt, peekFlowVariableString, pushFlowVariableDouble, pushFlowVariableInt, pushFlowVariableString, removeWarningListener, resetAndConfigureLoopBody, setInHiLiteHandler, setWarningMessage, stateChanged
protected PortObjectSpec configure(PortObjectSpec inSpecs) throws InvalidSettingsException
PortObjectSpecsthat are defined through the
PortTypesgiven in the
constructorunless this model is an
InactiveBranchConsumer(most nodes are not). Similarly, the returned output specs need to comply with their port types spec class (otherwise an error is reported by the framework). They may also be null (out spec not known at time of configuration) or inactive (output and downstream nodes are inactive).
For a general description of the configure method refer to the description of the specialized
NodeModel.configure(DataTableSpec) methods as it addresses more use cases.
inSpecs- The input data table specs. Items of the array could be null if no spec is available from the corresponding input port (i.e. not connected or upstream node does not produce an output spec). If a port is of type
BufferedDataTable.TYPEand no spec is available the framework will replace null by an empty
DataTableSpec(no columns) unless the port is marked as optional as per constructor.
InvalidSettingsException- If this node can't be configured.
protected PortObject execute(PortObject inObjects, ExecutionContext exec) throws Exception
inObjectsrepresent the input objects and the returned array represents the output objects. The elements in the argument array are generally guaranteed to be not null and subclasses of the
PortObject classesthat are defined through the
PortTypesgiven in the
constructor. Similarly, the returned output objects need to comply with their port types object class (otherwise an error is reported by the framework) and must not be null. There are few exceptions to these rules:
InactiveBranchConsumermay find instances of
InactiveBranchPortObjectin case the corresponding input is inactive.
InactiveBranchPortObjectelements in case the output should be inactivated.
For a general description of the execute method refer to the description of the specialized
NodeModel.execute(BufferedDataTable, ExecutionContext) methods as it addresses more use cases.
protected DataTableSpec configure(DataTableSpec inSpecs) throws InvalidSettingsException
For ordinary(*) nodes the passed DataTableSpec elements are never
null but can be empty. The model
null data table spec(s) for the outputs. Note, after the model has been executed this
function will not be called anymore, as the output DataTableSpecs are then being pulled from the output
DataTables. A derived
NodeModel that cannot provide any DataTableSpecs at its outputs before
execution (because the table structure is unknown at this point) can return an array containing just
null elements. As an example consider a "Transpose" node that flips columns to rows -- there is no
way to determine the table spec at time of configuration as the number of rows (which is the number of new
columns at the output) is unknown though the node is still executable.
(*)For nodes that support optional inputs or may have inactive outputs it's better to override
Implementation note: This method is called from the
NodeModel.configure(PortObjectSpec) method unless that
method is overwritten.
inSpecs- The input data table specs (as many as this model has inputs). Do NOT modify the contents of this array. If no spec is available for any given port (because the port is not connected or the previous node does not produce a spec) the framework will pass an empty
DataTableSpec(no columns) unless the port is marked as
optional(in which case the array element is null).
nullDataTableSpec elements are changed to empty once.
InvalidSettingsException- if the
#configure()failed, that is, the settings are inconsistent with given DataTableSpec elements.
protected void onDispose()
protected void reset()
NodeModel. All components should unregister themselves from any observables (at least from the hilite handler right now). All internally stored data structures should be released. User settings should not be deleted/reset though.
protected void validateSettings(NodeSettingsRO settings) throws InvalidSettingsException
NodeSettingsobject. The specified settings should be checked for completeness and consistency. It must be possible to load a settings object validated here without any exception in the
#loadValidatedSettings(NodeSettings)method. The method must not change the current settings in the model - it is supposed to just check them. If some settings are missing, invalid, inconsistent, or just not right throw an exception with a message useful to the user.
settings- The settings to validate.
InvalidSettingsException- If the validation of the settings failed.
protected void loadValidatedSettingsFrom(NodeSettingsRO settings) throws InvalidSettingsException
#validateSettings(NodeSettings)method. The model must set its internal configuration according to the settings object passed.
protected void saveSettingsTo(NodeSettingsWO settings)
NodeSettingsthe model specific settings. The settings don't need to be complete or consistent. If, right after startup, no valid settings are available this method can write either nothing or invalid settings.
Method is called by the
Node if the current settings need
to be saved or transfered to the node's dialog.
settings- The object to write settings into.
protected void loadInternals(File nodeInternDir, ExecutionMonitor exec) throws IOException, CanceledExecutionException
NodeModel. This method is only called if the
Nodewas executed. Read all your internal structures from the given file directory to create your internal data structure which is necessary to provide all node functionalities after the workflow is loaded, e.g. view content and/or hilite mapping.
nodeInternDir- The directory to read from.
exec- Used to report progress and to cancel the load process.
IOException- If an error occurs during reading from this dir.
CanceledExecutionException- If the loading has been canceled.
protected void saveInternals(File nodeInternDir, ExecutionMonitor exec) throws IOException, CanceledExecutionException
NodeModel. This method is only called if the
Nodeis executed. Write all your internal structures into the given file directory which are necessary to recreate this model when the workflow is loaded, e.g. view content and/or hilite mapping.
nodeInternDir- The directory to write into.
exec- Used to report progress and to cancel the save process.
IOException- If an error occurs during writing to this dir.
CanceledExecutionException- If the saving has been canceled.
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.