An effort to rationalize events happening around us - mostly software engineering !!

Wednesday, July 8, 2009

From JSF to Richfaces to Richfaces Portlet

We are going to start with a very simple JSF web application then convert that to a very simple Richfaces web application and then ultimately convert that Richfaces web application to Richfaces Portlet. This tutorial assumes that you have basic knowlege of JSF. All code used in this tutorial are at http://anonsvn.jboss.org/repos/qa/prabhat/. This application simply gives you some financial advice based on your age and your current savings. We all need some financial advice these days, don't we? ;-)

For an XHTMl page, you would need <xmlns:a4j="http://richfaces.org/a4j"> <xmlns:rich="http://richfaces.org/rich">

Just doing these changes will make your page look pretty i.e. Rich.

From

To

Note:1. If you deploy these app into JBoss AS, you do not need to bundle jsf jars in your war but you need them when deploying in tomcat.2. Adding Richfaces config and binaries to an existing JSF project is very simple using JBoss Tools or JBDS. You simply add "Richfaces Capabilities".

Converting a Richfaces application to Richfaces Portlet

Since Portlets run on portal server, converting a web app to portlet is not that straightforward. I guess that's why there is no add "Portlet Capabilities" in JBoss Tools/JBDS. But it's equally easy to get started using Maven archetypes. Portlet based on JSF/Richfaces/Struts run on a portal server through portlet bridge. There is a separate project called JBoss Portlet Bridge which allows you to do that that for JSF/Richfaces/Seam based portlets. This project provides different maven archetypes to get you quickly started with these portlets. For richfaces based portlet, you would need to do

The archetype will create all required deployment descriptors portlet.xml,portlet-instances.xml, jboss-portlet.xml which you of course would need to update. We are going to import richfaces pages we created previously to this project and modify deployment descriptors accordingly. The important changes are portlet and portal server specific deployment descriptors and hooking up bridge with JSF.

1. Portlet Bridge's view handler and state manager on top of JSF/RichfacesModify faces-config.xml so that it has<application><view-handler>org.jboss.portletbridge.application.PortletViewHandler</view-handler><state-manager>org.jboss.portletbridge.application.PortletStateManager</state-manager></application>

2. The Bridge Portlet to wrap xhtml as a view state of portlet<portlet><portlet-name>SimpleRichfacesPortlet</portlet-name><portlet-class>javax.portlet.faces.GenericFacesPortlet</portlet-class><init-param><name>javax.portlet.faces.defaultViewId.view</name><value>/introduction.xhtml</value></init-param><init-param><name>javax.portlet.faces.preserveActionParams</name><value>true</value></init-param><expiration-cache>-0</expiration-cache><supports><mime-type>text/html</mime-type><portlet-mode>VIEW</portlet-mode></supports><portlet-info><title>Simple Richfaces Portlet</title></portlet-info></portlet>

We are configuring that GenericFacesPortlet is the portlet, it supports view mode and for default view, we are going to use introduction.xhtml that we created in JSF and Richfaces.

3. portlet-instances.xml does not change in this context i.e it's same as that of any java portlet