Runtime Bundle

The runtime bundle contains the code related to business logic implementation and unit test.

Open the child TIBCO Business Studio configured with the bw-runtime platform, and then expand the runtime bundle in the Project Explorer view, the following files and folders are displayed:

Folders and Files Description
src Contains the source code to implement the business logic of each activity.
  • The runtime package contains the following files:
    • The PaletteNameContants.java file contains the defined constants used in the code.
    • The RuntimeMessageBundle.java file contains the bundle message definition.
    • The ActivityNameActivityType.java file contains the business logic of the activity, including the logic information on how to get configurations and input of the activity, and how to generate output according to design-time configurations.
    • The Resources.properties file contains the implementation of bundle messages and error codes.
  • The fault package contains the following files:
    • The PaletteNameActivityBaseException.java file contains the errors specified for the synchronous and asynchronous activities.
    • The PaletteNameActivityLifecycleFault.java file contains initialization errors.
    • The PaletteNamePluginException.java file contains the error defined by BusinessWorks Plug-in Development Kit by default.
    • The FaultNameFault.java file contains the generated fault schema according to the design-time configurations. Use the private <N, A> N constructErrData () method and the public QName getFaultElementQName() method to add other faults at run time. The private <N, A> N constructErrData () method is generated only when you add a customized fault at design time. If you do not specify any fault schema at design time, this file is not generated.
    Note: The PaletteNameActivityBaseException.java file is not available for the signal-in and process starter activities.
  • The pojo package contains Java Architecture for XML Binding (JAXB) generated common Java classes according to the output configurations. You can assign values to these POJO classes.
  • The util package contains the following files:
    • The PaletteNamePluginLogger.java file contains the generated logging utility.
    • The PaletteUtil.java file contains the generated output utility.
unit-test Contains the source code for unit tests.
META-INF Contains a MANIFEST.MF file that provides information regarding the plug-in bundle and package.
OSGI-INF Contains configuration files of OSGI bundles. Each activity corresponds to a bundle file.