During NodeFactory loading:
Use-case 1: Unknown input type
When auto-generating nodes from Plugins we have to make sure that all required=true inputs can be either mapped to Widget or mapped to a column in a KNIME table. If an input type can't be mapped, the node can't be created. We should write a warning in the KNIME log. Important: If someone enforces a column selection and we can't find a corresponding KNIME type for the java-type of the input parameter, but there exists a widget, we would't create the node anyway!
Use-case 2: Unknown output type
If we can't map an output-type of a Plugin to a KNIME type we can either create a StringCell and fill the contents with toString() or simply ignore this column. @Squareys @hornm any preference? Either way, we have to be transparent what's happening (hint in console, details in log).
During
NodeFactoryloading:Use-case 1: Unknown input type
When auto-generating nodes from
Pluginswe have to make sure that allrequired=trueinputs can be either mapped toWidgetor mapped to a column in a KNIME table. If an input type can't be mapped, the node can't be created. We should write a warning in the KNIME log. Important: If someone enforces acolumn selectionand we can't find a corresponding KNIME type for the java-type of the input parameter, but there exists a widget, we would't create the node anyway!Use-case 2: Unknown output type
If we can't map an
output-typeof aPluginto a KNIME type we can either create aStringCelland fill the contents withtoString()or simply ignore this column. @Squareys @hornm any preference? Either way, we have to be transparent what's happening (hint in console, details in log).