|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
The Java class file must be located in the classpath for TIBCO Designer and the TIBCO ActiveMatrix BusinessWorks process engine. Update the designer.tra and bwengine.tra file to contain the directory where your Java class files are located.See Common Features of Java Code and Java Method for more information about features available in the Java Code activity.
You can execute methods on shared Java objects created by Java Global Instance resources by specifying the resource in this field. See Java Global Instance for more information about the shared Java objects created by Java Global Instance resources.Note: If the configuration of the Java Global Instance resource changes, you must select and view any Java Method activities in your process definitions that reference the Java Global Instance to automatically propagate the changes. An exception is raised if you attempt to test your process definitions before refreshing the reference to the Java Global Instance. You may need to manually update the mappings of any input or output if you select a new method with a different signature in the Java Global Instance resource. Use this field to specify an AliasLibrary resource that is used to locate the Java class files. See TIBCO Designer Palette Reference for more information about AliasLibrary resources. The declared Java class whose method you want to execute. Use the Show Class Browser button to select the class and method, or use the Java Global Instance field to specify a shared Java object. The method in the selected Java class you want to execute. This field is automatically populated when you use the Show Class Browser button.Note: You can hover the cursor over this field to display the signature of the selected method.
When this field is unchecked, you must supply an object reference for the Java class specified on the Configuration tab. The object must be created and contained in the output schema of a previously executed activity, such as a Java Code activity, another Java Method activity, a RMI Server process starter, or an XML To Java activity. In this case, the declaring class is included in the activity’s input schema. See Caching the Java Class for more information about caching the declared class. When the Cache Constructed Class check box is selected on the Advanced tab, all instances of the same Java method activity share the same Java object. For example, each process instance that executes this Java Method activity will share the same instance of the class.Also, if this activity is executed multiple times in a loop, each execution of this activity uses the same cached instance of the object. Figure 16 illustrates multiple processes and Java Methods in a group all sharing the same Java class.
Figure 16 Sharing a cached classHowever, different instances of a Java Method activity that invoke methods on the same class do not share the instance of the object. For example, Figure 17 illustrates two Java Method activities in the same process definition, each executing different methods on the same Java object. However, each of these Java Method activities operate on their own instances of the inv class, if they both select the Cache Constructed Class check box.In the process definition illustrated in Figure 17, for each process instance that is created, each time the inv.CheckInventory activity executes, it shares one instance of the inv object that has been cached. Similarly, each time the inv.DecreaseInv activity executes, it shares the instance of the inv object that the activity has cached. However, the inv.CheckInventory and inv.DecreaseInv activities do not share their cached Java objects with each other.See TIBCO ActiveMatrix BusinessWorks Process Design for more information about mapping and transforming input data.
<declaringClass>
<exceptionName> <exceptionName> The exception class name. The value of this element is obtained by calling the <exception>.getClass().getName() method. The exception message. The value of this element is obtained by calling the <exception>.getMessage() method.
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |