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.
Table 6.36. a4j : portlet attributes
Attribute Name | Description |
---|---|
binding | The attribute takes a value-binding expression for a component property of a backing bean |
id | Every component may have a unique id that is automatically created if omitted |
rendered | If "false", this component is not rendered |
Table 6.37. Component identification parameters
Name | Value |
---|---|
component-type | org.ajax4jsf.Portlet |
component-family | org.ajax4jsf.component.Portlet |
component-class | org.ajax4jsf.component.html.HtmlPortlet |
To create the simplest variant on a page use the following syntax:
<f:view>
<a4j:portlet>
...
</a4j:portlet>
</f:view>
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.
On RichFaces LiveDemo page you can found some additional information for <a4j:portlet> component usage.
The aditional information about component usage you can find here: Ajax4Jsf Users Forum.
Portlet Sample could be checked out from JBoss SVN: portal-echo application.
Usage instructions for this demo could be found at the corresponding: portal-echo application.