Using Java Beans

Generated Java beans can be used to add host access tasks to applications created in any Java application development environment. Each bean includes additional read-write and read-only methods representing the inputs and outputs built into the task. Using Task Builder, you can generate two types of Java beans:

• Task Beans. Task beans are Java beans that contain a single task for each bean and implement the ITask interface. Each bean includes set and get methods as well as set methods representing the inputs and outputs built into the task. When you generate task beans a set of Javadocs describing the methods available in the bean is also created.

• Service Beans. Service beans are also Java beans but, unlike task beans, they can include multiple tasks in a single bean. Service beans contain one method for each task. The input bean is the parameter to the method with the same name as the task, and the return value of the method is the output bean.

Using Java Beans

To see files generated by Task Builder, and their locations, see these two topics: Generating Task Bean Interface Objects, and Generating Service Bean Interface Objects.

When writing code to access your tasks through Java beans, you should typically follow this workflow:

1. Instantiate the bean.
2. Set the bean's input properties.
3. Execute the task.
4. Get the bean's output properties.
5. Terminate the bean.

Since each service bean can contain more than one task, you would repeat steps 2 through 4 until each task has been executed.

Service Beans with Apache Axis Web Services

When you generate Web services for Apache Axis, a bean is generated, which is essentially identical to a service bean, but includes a Web Service Deployment Descriptor (WSDD) for deployment to the Apache Axis server. A WSDD is an XML document for configuring Apache Axis Web services.

	Using Tasks in Your Applications
	ITask Sample Code
	Task Bean Input and Output Examples
	Attachmate Javadocs