Jolt 1.2 Developer's Guide
Table Of Contents
- Jolt for NonStop(TM) TUXEDO Developer's Guide
- Jolt for NonStop(TM) TUXEDO Developer's Guide
- About This Guide
- 1. Introducing Jolt
- 2. Installing Jolt
- 3. Configuring the Jolt System
- 4. Bulk Loading NonStopTM TUXEDO Services
- 5. Using the Jolt Repository Editor
- 6. Using the Jolt Class Library
- 7. Using JoltBeans
- 8. Using Servlet Connectivity for NonStopTM TUXEDO
- 9. Using Jolt 1.2 ASP Connectivity for NonStopTM TUXEDO
- A. NonStopTM TUXEDO Errors
- B. System Messages
- Index

Using Custom GUI Elements With the JoltService Bean
JoltBeans provides a limited set of GUI components. You can also use controls that are not Jolt-enabled together with
the JoltServiceBean. You can link controls to the JoltServiceBean that display output information of the service
represented by the JoltServiceBean. You can also link controls that display input information.
For example, the GUI element that uses an adapter class to implement the JoltOutputListener interface can listen to
JoltOutputEvents. The JoltServiceBean as the event source for JoltOutputEvents calls the serviceReturned() method of
the adapter class when it sends a JoltOutputEvent. Inside serviceReturned(), the control's internal data is updated using
information from the event object.
The development tool generates the adapter class when the JoltServiceBean and the GUI element are wired together.
As another example, a GUI element can call the setInputTextValue() method on the JoltServiceBean. The GUI element
contains input data for the NonStop
TM
TUXEDO service represented by the JoltServiceBean.
As a third example, a GUI element can implement the required methods (addJoltInputListener and
removeJoltInputListener) to act as an event source for JoltInputEvents. The JoltServiceBean acts as an event listener for
these events. The control sends a JoltInputEvent once its own state changes to keep the JoltServiceBean updated with
the input information.










