Developing Portlets

You are viewing an old version (v. 6) of this page.
The latest version is v. 7, last edited on Apr 18, 2018 (view differences | )
<< View previous version | view page history | view next version >>

Developing Your Own Portlets


ICEfaces makes use of the PortletFaces Bridge to handle the mapping of the portlet lifecycle onto the JSF lifecycle. This has many advantages like enabling proper resource handling and cleaner integration with the portal container. To define your portlet, specify the following:

            <title>ICEfaces Portlet Chat</title>
            <keywords>icefaces portlet chat icepush</keywords>

If you are using the PortletFaces Bridge, the portlet-class needs to be defined as:


The LiferayFaces Bridge is backwards compatible in this regard so if you are migrating from PortletFaces to LiferayFaces, the older classname will still work.


To prevent the processing of portlet resource URLs to avoid caching of things like bridge.js, the following parameter should be set to false.


Library Dependencies

You must use a portlet bridge to run JSF and ICEfaces portlets in a portal container. See the section on Portlet Bridges for more information.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

© Copyright 2017 ICEsoft Technologies Canada Corp.