Because portlet events have arbitrary payloads the bridge provides no automated mappings to managed beans. Instead, the bridge calls the handleEvent method on the BridgeEventHandler instance passed to it (via a PortletContext attrbiute at init time. This method is expected to update any models based on the event's payload and then to perform any needed application recomputation to ensure a consistent state. The method is called after the FacesContext has been established and the Lifecycle has restored the view.
A view navigation can be affected by returning a non-null EventNavigationResult. Such an object will contain two String values: a fromAction and an outcome. These correspond to the from action and outcomes in Faces navigation rules. Using this information the bridge affects the navigation by calling the Faces NavigationHandler.
@param context current FacesContext. A Lifecycle has been acquired and the current view restored.
@param event the portlet event. Other portlet information (request/response) is accessed via the ExternalContext.
@return an object containing the fromAction and outcome of any navigation that resulted from this event.If the event doesn't cause a navigation, return null.
The handleEvent method is invoked by the JAXB provider, if a problem was found. The events {@link javax.xml.bind.ValidationEventLocator} may beused to locate the source of the problem.
EventListener interface was registered.
@param evt The Event contains contextual information about the event. It also contains the stopPropagation and preventDefault methods which are used in determining the event's flow and default action.
| |
| |
| |
| |
| |
| |
| |
| |
| |