IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

HTML flow processor

The toolkit provides an implementation of a specialized Automaton for supporting HTML client requests on the server. The specialized Automaton is a state machine that can handle multiple execution hits and reply to each hit according to a defined flow. It provides a flow processor (DSEHtmlProcessor) that controls navigation within the client by performing different actions depending what the user selects in a dialog. The navigation process represents each dialog as a state in the navigation process.

The DSEHtmlProcessor extends the DSEProcessor class and adds the following functionality to the generic flow processor:

When the HTML flow processor is in the page state, it resumes control of the flow when it receives an event from an HTML page containing a field in which the user has done something. The value for the field determines the name of the event (dse_nextEventName) raised by the page.

When the HTML flow processor is in the subFlow state, it raises a subflow running in a child processor. The processor resumes control of the flow when it receives an event from the child processor. The name of the event is the value of the typeIdInfo attribute of the final state of the child processor.

During a flow, the HTML flow processor enters the page and subflow states twice. The first time occurs before the processor releases control and the second time occurs when it resumes control. During the first state entry, the toolkit executes the entry actions without triggering the event listeners. During the second state change, the toolkit processes the event normally. Once the processor loses control, the toolkit stores relevant processor information such as the processor's context and then deletes the processor instance from memory. When it is time for the processor to regain control, the toolkit recovers the processor instance using the stored information. Before the toolkit stores the processor context, the toolkit unchains it from its parent, which is the session context. This means that the HTML flow processor's context must not have a defined parent.

The following two HTML flow processor examples are provided:


Feedback