With the release of JSF 2 and ICEfaces 2, a common situation arises of porting and converting existing ICEfaces 1.8.x applications. This tutorial will demonstrate the required steps to convert a legacy application to "compat mode" in ICEfaces 2. This means you can still use your existing ice: components and backing beans, but aren't yet taking advantage of ICEfaces 2 specific features and benefits. The majority of the conversion effort involves configuration files and libraries, so most of your page markup won't need to be significantly changed.
This tutorial assumes the reader has a basic understanding of JSF and ICEfaces, especially creating and working with projects related to those technologies. The focus is not to teach the foundations, but instead to learn about porting applications. More information about porting can also be found [here].
The goal of this tutorial is to examine a real world ICEfaces 1.8.x application. Once we have an understanding of the project we will begin the steps to port the application to ICEfaces 2. The application is a slightly modified version of the "jobApplication" used in the ICEfaces Online Training. There is a central form based page that can redirect to two pages based on different outcomes.
The following tools were used to create the project.
- Eclipse IDE for Java EE Developers - Version Galileo
- Tomcat 6.x Web Server
- Java 6.x
- ICEfaces 1.8.2 and ICEfaces 2
|jobApplication 1.8 project||[jobApplication 1.8 source code |Converting ICEfaces 1.8 Applications to ICEfaces 2^jobApplication-1.8.zip|Download Source Code]||The Eclipse workspace of the jobApplication project written in ICEfaces 1.8.|
Download and extract the above source code bundle, and Import -> Existing Project into Workspace the folder into your Eclipse instance. Build and deploy the application to your Tomcat instance, and navigate to the deployed jobApplication. You will see a page similar to the following:
Now let's examine the page code, to get a better idea of what the application is doing. There are three main pages:
- applicantForm.xhtml** Main page that has a series of internationalized form fields with validation, partialSubmit, a ice:selectInputDate component, etc.
- noThanks.xhtml** Basic page redirected to when the first name equals "John".
- thankYou.xhtml** Similar page redirected to when the first name is anything else.
The Java code is fairly standard for 1.8, focusing on two beans:
- bean.backing.ApplicantForm.java** Controller/backing bean for the applicantForm.xhtml page. This controls the submission and some of the rendering toggles on that page.
- bean.model.Applicant.java** Model object containing variables for the different Applicant fields, like First Name and Travel Percentage. No UI specific functionality.
- Supporting Beans
- The ProvinceSupport.java and Province.java classes are used to back the available items in the ice:selectOneMenu found on the main page.
- The messages_en.properties and JSF-override_en.properties are used to internationalize the various form labels.
Now that we understand the project, we'll start the 1.8 to ICEfaces 2 conversion process. The steps below will help you understand the requirements of porting, and can be applied to any of your own projects.
Currently jobApplicaiton is using ICEfaces 1.8.2 and JSF 1.2. We will want to upgrade these versions to 2.
First remove references in our project to ICEfaces 1.8.2 and JSF 1.2. This will likely require Build Path changes inside Eclipse. The ICEfaces Core, Facelets, and Support Libraries 1.8.2 should be removed, as should JSF 1.2 Sun RI. The exact naming may be different in your project.
Download and extract the ICEfaces 2 bundle, and copy the following jar files from icefaces/compat/lib/ to jobApplication/WEB-INF/lib/:
The primary jars are icefaces.jar and icefaces-compat.jar. The former contains all the ICEfaces 2 code we need, while the latter has compat specific code around ice: components.
Now we will add JSF 2. There are two jars we need to reference in icefaces/lib/ called jsf-api.jar and jsf-impl.jar. The recommended approach is to create a custom User Library in your Eclipse project, but the jars could also be copied to the jobApplication/WEB-INF/lib/ folder.
There will probably be a few errors within the project because of these changes. That's okay, we just need to modify the configuration and pages to be 2 specific to resolve this problem.
Now we will change the XML configuration file faces-config.xml. The main changes will be scope related, to accomodate the new JSF 2 scopes.
First we'll update the faces-config.xml header to be 2, instead of 1.2. Near the top of the file replace:
As you can see we changed the version and schema location to 2.
Now we can remove the old reference to the D2DFaceletViewHandler, as this customization is handled transparently in ICEfaces 2. Remove the following line inside the <application> node:
Next we will modify the old <managed-bean-scope> nodes to conform to those available in ICEfaces 2. Previously ICEfaces 1.8.x used "extended request scope", which meant request was handled differently than it is now. The closest we can get to duplicating this functionality is using the new view scope.
Change all 3 beans to have a scope of view:
Now we will change the XML configuration file web.xml. The main change will be servlet mappings and adding some context parameters for ICEfaces 2.
The previously declared Persistent Faces Servlet and Blocking Servlet are no longer needed in ICEfaces 2, as their functionality has changed and setup has been reduced. Remove all declarations and mappings for those two servlets:
As part of the compatibility requirements of porting a project, a new servlet will be added:
The purpose of the FacesServlet has changed between 1.8 and ICEfaces 2, and so the declaration and mapping must as well. Replace the old declaration:
With the new declaration and mapping:
The last change in web.xml is to change some of the context-param variables. Replace the old variables:
With a pair of new context-param variables that help ICEfaces 2 act more like 1.8.x in regards to markup and validation:
The final change is to modify the page markup to conform to ICEfaces 2 standards. These changes are mostly related to the header and format of the page, while all the ice: components can remain as they are.
The first page to change is the simplest, and that is modifying that page index.jsp redirects to. Change the old redirect:
To point to the new mapping extension of the applicationForm page:
As mentioned the header, namespace, and body tags need to be modified to port 1.8 markup to ICEfaces 2. Replace the following tags near the top of the page:
With the following:
Remember to replace all closing tags for the above changes.
This change was necessary because ICEfaces 2 uses html as the parent container tag of a page, instead of f:view. Also h:head and h:body are used instead of the old plain HTML head and body.
Similary the headers of our other two pages will need to be changed. Replace the old header code in both pages:
With a similar update:
As before, remember to update the closing tags as well.
The ice:outputDeclaration tag has been deprecated for ICEfaces 2 and should be replaced with the DOCTYPE tag. Remove the following:
Replace it with:
Those are all the changes we needed! Overall porting 1.8 to ICEfaces 2 is fairly simple, and focuses more on configuration changes instead of being forced to modify your Java code or any functional markup.
Build and re-deploy the jobApplication and test it to ensure the functionality remains the same. From a user point of view the page will look the same, but now we're running on the modern ICEfaces 2!
The resulting code for the ICEfaces 2 version of the jobApplication is available if you need.
|jobApplication 2.0 project||[jobApplication 2.0 source code |Converting ICEfaces 1.8 Applications to ICEfaces 2^jobApplication-2.0.zip|Download Source Code]||The Eclipse workspace of the jobApplication project written in ICEfaces 2.|