Development effort

The flow processor should not directly handle all of the events shown in the diagram. The navigation controller should internally handle some events such as the ones associated with the cancel, next and back buttons. For example, you should configure the buttons to fire navigation events instead of action events, which allows the navigation controller to manage the view navigation and to defer handling the service invocation tasks to the flow processor.

The processor instantiates views by name using the views externalizer. When used in this way, the views do not have a specific context. Instead, they use the processor context. Both the navigation controller and the actions for opening views can assign the processor context to the panels. In the example, the navigation controller assigns the processor context to the panel when it opens the second view, but actions assign the processor context when the processor opens any of the other views.

Refer to the Navigation Controller and visual beans documentation for more information on the events generated by the panel and the buttons.