# tJavaFlex Standard properties

These properties are used to configure tJavaFlex running in the Standard Job framework.

The Standard tJavaFlex component belongs to the Custom Code family.

The component in this framework is available in all Talend products.

## Basic settings

| Schema and Edit<br>Schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br>Click Sync columns to retrieve<br>the schema from the previous component in the Job.<br><br>This<br>component offers the advantage of the dynamic schema feature. This allows you to<br>retrieve unknown columns from source files or to copy batches of columns from a source<br>without mapping each column individually. For further information about dynamic schemas,<br>see *Talend Studio*<br>*User Guide*.<br><br>This<br>dynamic schema feature is designed for the purpose of retrieving unknown columns of a<br>table and is recommended to be used for this purpose only; it is not recommended for the<br>use of creating tables. |
| --- | --- |
|  | Built-In: You create and store the schema locally for this component<br>only. |
|  | Repository: You have already created the schema and stored it in the<br>Repository. You can reuse it in various projects and Job designs.<br><br>When the schema to be reused has default values that are<br>integers or functions, ensure that these default values are not enclosed within<br>quotation marks. If they are, you must remove the quotation marks manually.<br><br><br>For more information, see the related<br>description of retrieving table schemas in Talend Studio User Guide. |
|  | Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion. If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |
| Data Auto Propagate | Select this check box to automatically propagate the data to the<br>component that follows. |
| Start code | Enter the Java code that will be called during the initialization<br>phase. |
| Main code | Enter the Java code to be applied for each line in the data<br>flow. |
| End code | Enter the Java code that will be called during the closing<br>phase. |

## Advanced settings

| Import | Enter the Java code that helps to import, if necessary, external<br>libraries used in the Main code box<br>of the Basic settings view. |
| --- | --- |
| tStatCatcher Statistics | Select this check box to gather the Job processing metadata at a<br>job level as well as at each component level. |

## Global Variables

| Global Variables | ERROR\_MESSAGE: the error message generated by the component when an<br>error occurs. This is an After variable and it returns a string. This variable functions<br>only if the Die on error check box<br>is cleared, if the component has this check<br>box.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>To fill up a field or expression with a<br>variable, press Ctrl + Space to<br>access the variable list and choose the variable to use from it.<br><br>For further information about variables, see *Talend Studio*<br>*User Guide*. |
| --- | --- |

## Usage

| **Usage rule** | You can use this component as a start, intermediate or output<br>component. You can as well use it as a one-component subJob. |
| --- | --- |
| Limitation | You should know the Java language. |