Important notes on saving a mapping and java code
Refer to these notes:
-
If the mapping was previously saved, notice that the mapping is unsaved, as indicated by an asterisk before the mapping name on the mapping tab. When you save the Java code in the Java editor, the code is inserted into the mapping, but the mapping is not saved.
An invisible
.java
file is created in your project but the file is not used by the mapping. To save your Java code it is important to also save the mapping. -
If you add, remove, or rename function parameters, global variables, or constants, save your work and then close the Java editor tab. Then, modify the Java code again to reflect these changes.
The Java skeleton is generated every time you select Edit Java Code for a function.