Developing Portlets

You are viewing an old version (v. 4) 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, take a look at the portlet definition of the chat portlet example:

            <title>ICEfaces 2 Chat</title>
            <short-title>ICEfaces 2 Chat</short-title>
            <keywords>icefaces portlet chat icepush</keywords>

The important parts are:

  • The portlet-class, which needs to be defined as org.portletfaces.bridge.GenericFacesPortlet.
  • The javax.portlet.faces.defaultViewId.view which should identify the page that is the initial view of the portlet.


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

The ICEfaces distribution includes a tested release version of the PortletFaces Bridge and is located in:

  • portletfaces-bridge-*.jar
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

© Copyright 2017 ICEsoft Technologies Canada Corp.