Generating All Project Class Files at the Command Line

You can generate all class files in a project at the command line. Although this is a core component, the class files are generally used within the context of TIBCO BusinessEvents Decision Manager, where decision table class files can be separately deployed.

Note: This is a TIBCO BusinessEvents tool and it does not by default save classes to the RMS project directory. Instead you specify a location in the command.

You must place the class files in the location where a class loader picks up files for loading, and you must exclude all unwanted files from being loaded. See Generated Files Location for details.

Procedure

  1. Navigate to BE_HOME/studio/bin/ and open a command prompt.
  2. Execute a command with the following format (all on one line) at a command prompt: 
    studio-tools -core generateClass [-h] -p studioProjectDir [-n studioProjectName] -o outputPath [-x {true | false}] [-lc] [-pl projectLibraryFilePath] [-cp extendedClasspath]

    For example: 

    studio-tools -core generateClass -p D:\Workspace\FraudDetection -o c:\temp -x true -cp c:\tibco\be\5.2\lib\myjar.jar

    Table 14, TIBCO BusinessEvents Studio Tools for Generating One Table’s Class Files, provides detailed information about the options.

    TIBCO BusinessEvents Studio Tools for Generating Class Files
    Option Description
    -core generateClass Within the core category of operations, specifies the generateClass operation used to generate a project's class files.
    -h Optional. Displays help.
    -p Absolute path to the TIBCO BusinessEvents Studio project directory.
    -n Optional. Specifies the name of the TIBCO BusinessEvents Studio project whose class files are to be generated. If not specified, the final (leaf) directory name in the path specified for the -p option is used as the project name.
    -o Specifies the output directory for generated classes.

    If you do not specify a directory, files are placed in a user temporary directory. For example, on Windows files might go in a directory like the following:

    C:\Documents and Settings\User\Local Settings\Temp\BE_1322046141896

    -x Optional. If true, overwrites any existing class file with the same name.
    -lc Optional. Specifies that the file-based legacy compiler must be used to build the EAR file. By default, the EAR files are built in memory.
    -pl Optional. Specifies list of project library file paths to be used, separated by a path separator.
    -cp Optional. Extended classpath. Use as needed. Provide separate JAR file paths for each JAR file required for project compilation. For example, additional classpath information is needed if the decision table uses custom functions or third-party JAR files.

    Separate entries by the appropriate path separator. For example if the separator is semicolon (;) you might add the following:

    C:\customjars\custom.jar;C:\customjars\custom2.jar

    You see a success message if the files were generated successfully.