Hi Jean-Marie,

I think you are right. Actual the transfer is based on simple strings. I took a closer look on the code but it is some month ago. But if I remember right all transfer is based on a string. Your data is not casted, th toString()-function is used. Later in the subJob the string is parsed. This is an additional (and not necessary) overhead, error-prone and limited to simple types.

But a change to this functionality would need a greater change in the overall class design and the components.

I tried another solution with the following code. In this example i take a list of values (1,2,3,4,5) each in one row into a list and try to transfer the data into a sub job.

dataInput -> tJavaFlex -> tRunJob

mainJob:
tJavaFlex

//start code
java.util.ArrayList dataList= new java.util.ArrayList();
ByteArrayOutputStream baos= new ByteArrayOutputStream();
ObjectOutputStream oos= new ObjectOutputStream(baos);

// main code
dataList.add(row2.testData);
row3.testData2= dataList;
oos.writeObject(dataList);
oos.flush();
row3.testData2= baos.toString();

//end code
oos.close();

subJob:
tJavaRow

ByteArrayInputStream bais = new ByteArrayInputStream(((String)input_row.data).getBytes());
ObjectInputStream ois = new ObjectInputStream(bais);
output_row.data= (String) ois.readObject();

The result is now an InvalidClassException because of the serialVersionUID. To resolve this issue I have to create a custom, modified ArrayList and stoped working for now.
But with this example it would be possible to transfer every object which implements "Serializable".

Bye
Volker