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
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.
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.
Table of <a4j:portlet> attributes.
Table 6.27. Component Identification Parameters
| Name | Value |
|---|---|
| component-type | org.ajax4jsf.Portlet |
| component-family | org.ajax4jsf.component.Portlet |
| component-class | org.ajax4jsf.component.html.HtmlPortlet |
Visit the Portlet page at RichFaces LiveDemo for examples of component usage and their sources.
Useful publications:
Ajax4Jsf Users Forum — check the forum for additional information about component usage;
portal-echo application — Portlet Sample, could be checked out from JBoss SVN;
First snapshot with Portal environment support contains usage instructions for the Portlet Sample demo.