The 329 specification is aimed at making the developers life as easy as possible with JSF+Portlet development. You will see below that there are minimal settings to getting any JSF web application up and running in the Portal environment.

When preserveActionParams is set to TRUE, the bridge must maintain any request parameters assigned during the portlet's action request. The request parameters are maintained in the"bridge request scope". When this attribute isn't present or is FALSE the action's request parameters are only maintained for the duration of the portlet request scope.

RenderPolicy Options

ALWAYS_DELEGATE Indicates the bridge should not render the view itself but rather always delegate the rendering.

NEVER_DELEGATE Indicates the bridge should always render the view itself and never delegate.

DEFAULT Directs the bridge to first delegate the render and if and only if an Exception is thrown then render the view based on its own logic. If the configuration parameter is not present or has an invalid value the bridge renders using default behavior. I.e. as if DEFAULT is set.

3.1.4. JSP Only Configuration

The following web.xml setting is only for JSP based applications. Download the demo application here.

3.2. RichFaces Setup and Configuration Options

3.2.1. web.xml

The following configuration is designated for portlets using the RichFaces library in GateIn. These settings will vary based on your individual needs. See this section of the RichFaces documentation for more details.

If you are using this bridge packaged from 2.0.0.BETA onward, you must define the following web.xml parameter to use the JBoss Portlet Bridge provided Seam Phase Listener.
This is done by the bridge automatically (if needed) in 2.0.0.FINAL.

3.4.2. Public Render Parameters

3.4.2.1. Configuration

Public Render Parameters (or PRPs) are one of the most powerful and simple Portlet 2.0 features. Several portlets (JSF or not) can share the same render parameters. This feature can be use to present a cohesive UI to the user across all portlets on the page (i.e. using an employee ID to display relative data).