When you generate a task bean, a Java package is created in a folder named for the task file from which the bean was generated. The default location for the folder created is:
install_location\EAI\CICSTaskDesigner\MetaData\task_file_name
A Java package name consists of descriptive parts, with a period between each part. Typically, the first part of the package name indicates a logical grouping for similar packages. The remaining parts describe the package, or what is contained in the package. The package name also represents the directory structure of the package.
In Task Builder, when you specify a package name, any class file created is given a fully qualified name by appending the name of the task file used to generate the bean to the package name specified. For example, if you had a task file named StockSale, and a bean generated from that file, and you specified a package name of com.attachmate.tasks, the class file created would be named com.attachmate.tasks.StockSale.
If a task file contains more than one task, a separate Java class would be generated for each task. The names of the tasks would be identical except for the last part, which would reflect the name of the task for which it is created. For instance, if the task file contained two tasks, named Task1 and Task2, the classes created would be named com.attachmate.tasks.Task1 and com.attachmate.tasks.Task2.
To generate a task bean interface object | ||
---|---|---|
|
![]() |
|
![]() |
Creating Task Files |
![]() |
Creating a Task Definition |
![]() |
Generating Service Bean Interface Objects |
![]() |
Using Apache Axis Web Services |
![]() |