Create new RichFaces Documentation Jira issue

This will launch the RichFaces Jira page - to complete your feedback please login if needed, and submit the Jira.

JBoss.orgCommunity Documentation

6.5.2.  < a4j:portlet > available since 3.0.0

The <a4j:portlet> component is DEPRECATED as far as JSR-301 was defined a same functionality for a UIViewRoot component. Thus, it is implicitly defined by mandatory <f:view> component.

Table 6.50. a4j : portlet attributes

Attribute Name Description
binding JSF: The attribute takes a value-binding expression for a component property of a backing bean
id JSF: Every component may have a unique id that is automatically created if omitted
rendered JSF: If "false", this component is not rendered

Table 6.51. Component identification parameters


To create the simplest variant on a page use the following syntax:


import org.ajax4jsf.component.html.HtmlPortlet;
HtmlPortlet myPortlet = new HtmlPortlet();

The main component purpose is realization of possibility to create several instances the same portlet on one page. But clientId of elements should be different for each window. In that case namespace is used for each portlet. The <a4j:portlet> implemets NaimingContainer interface and adds namespace to all componets on a page. All portlet content should be wrapped by <a4j:portlet> for resolving problems mentioned before.

Vizit the Portlet page at RichFaces LiveDemo for examples of component usage and their sources.

Useful publications: