The JoltBeans toolkit provides a JavaBeans compliant interface to BEA Jolt.
The JoltBeans toolkit contains beans which wrap the existing Jolt class library into reusable bean components, such as the JoltSessionBean or the JoltServiceBean. These beans can be customized easily by giving application specific values to properties and connecting them with other bean components.
You can use the JoltBeans toolkit with your Integrated Development Environment (IDE) to create Jolt clients that can access a TUXEDO application.
This section includes the following topics:
The JoltBeans product includes a set of .jar files that you can import to your IDE. For example, if your IDE is Symantec Visual Cafe´, "drag and drop" the .jar file into the Component Library window of Visual Cafe´.
Note:
Currently, Symantec Visual Cafe´ 2.5 is the only IDE that has been certified by BEA for use with JoltBeans.
Refer to the following terms as you work with JoltBeans:
How JoltBeans Work
JoltBeans Terms
During development, drag the beans from the JoltBeans component palette of your development environment to the Java form designer for a Jolt client application or applet. You must populate the properties of the beans (see Table 3-6) and set up the event source-listener relationships between various beans of the application or applet. The development tool typically generates the event hook-up code. Finally, add the application logic to the event callbacks.
Java Beans communicate via events. The concept of events in a BEA TUXEDO system and events in a JavaBeans environment differ. In a TUXEDO application, an event is raised from one part of an application to another part of the same application. JoltBeans events are events that communicate between beans. See "Using TUXEDO Event Subscription and Notification with JoltBeans" in Chapter 3, "Using JoltBeans," for more information.
A Jolt client applet or application that has been built using JoltBeans typically consists of Jolt aware AWT beans, such as JoltTextField or JoltList, and JoltBeans, such as JoltServiceBean and JoltSessionBean. The main mode of communication between beans is by JavaBeans events.
Jolt aware beans are sources of JoltInputEvents or listeners of JoltOutputEvents or both. JoltServiceBeans are sources of JoltOutputEvents and listeners of JoltInputEvents.
The Jolt aware AWT beans expose properties and methods so you can link the beans directly to parameters of a TUXEDO service (represented by a JoltServiceBean). Jolt aware beans notify the JoltServiceBean via JoltInputEvent when their content changes. The JoltServiceBean sends a JoltOutputEvent to all registered Jolt aware beans when the reply data is available after the service call. The Jolt aware AWT beans contain logic that update their contents with the corresponding output parameter of the service
Figure 1-1 shows a graphical representation of the possible relationships among the JoltBeans.
Figure 1-1 Possible Interrelationships Among the JoltBeans