Defining the IWrappers, which should be called (using SELWRP), and setting direct page jumps within the view has a lot of drawbacks (e.g. maintenance effort/replication for different countries, strong view-logic coupling, implicit view component dependencies). The problem should be solved using actions, which explicitly define dependencies, e.g. as part of the page request configuration.
An action has to be defined in the view-logic layer, replaces SELWRP, and can encapsulate jumps and submits to other pages. View-logic components export it as part of their interface. An action can be in a defined state (available, not available).
Action meta-informations should be displayed in the DOM tree (including their state) and can be used for content assist in the Pustefix editor.
Some of these requirements are already implemented (see #12 and #31).
