Generation of Java Code

Section - Java Deployment

When building transforms,  TM Design Tool takes model meta-data and SML code and generates the resulting transform in pure Java code.  All generated Java code is automatically compiled to Java byte code and then added to the generated .jar file.   This code may then be run on any Java VM (1.3 and above) to perform data transformations.

All generated Java code is automatically compiled to Java byte code and then added to a generated .jar  file.   

Two settings in the TM Design Tool GUI affect the building and location of the .jar  file.

• Tools | Preferences | SML Generation | Jar Deployment Destination specifies the location of the .jar file
• Tools | Preferences | SML Generation | Remove Generated Code specifies that all code other than the Java file should be removed after the .jar file is built.

The ".jar" file name is set automatically, and cannot be modified.  Given a project name of "NAME" and a version of "XX", the name of the ".jar"  file will be ETL_NAME_XX_0.jar  In order to deploy the transformation project all that is necessary is that the generated .jar file (and of course the invariant standard library ofetsr.jar supplied with TM) is added to the Java classpath.

Alternatively it is possible to include the Java code itself provided that Edit | Settings | SML Generation | Remove Generated Code setting is not set. This may be desirable if you use a Java source code debugger - such as Borland's JBuilder  - on the generated Java code. This should be considered an expert use of the system.