There are two ways to find a JSF portlet’s dependencies for Liferay DXP 7.0:
- The http://liferayfaces.org/ home page lets you look up the dependencies (Gradle or Maven) by Liferay DXP version, JSF version, and component suites.
- The Liferay Faces Version Scheme article’s tables list artifacts by Liferay DXP version, JSF version, portlet version, and AlloyUI and Metal component suite version.
In this tutorial, you’ll see how easy it is to upgrade a Liferay Portal 6.2 JSF portlet (JSF 2.2) to Liferay DXP 7.0 by upgrading the sample JSF Applicant portlet. This portlet provides a job application users can submit.
For reference, you can download the pre-upgraded portlet code and the upgrade portlet code. This sample project uses Maven.
Follow these steps to upgrade your Liferay JSF portlet.
Open your Liferay JSF portlet’s build file (e.g.,
build.gradle) to where the dependencies are configured.
Navigate to the http://liferayfaces.org/ site and generate a dependency list by choosing the environment to which you want to upgrade your portlet.
Compare the generated dependencies with your portlet’s dependencies and make any necessary updates. For the sample JSF Applicant portlet, only one Liferay Faces dependency requires updating:
<dependency> <groupId>com.liferay.faces</groupId> <artifactId>com.liferay.faces.bridge.ext</artifactId> <version>3.0.0</version> </dependency>
The Liferay Faces Bridge EXT dependency must be updated to version 5.0.0 for Liferay DXP 7.0. The updated dependency should look like this:
<dependency> <groupId>com.liferay.faces</groupId> <artifactId>com.liferay.faces.bridge.ext</artifactId> <version>5.0.0</version> </dependency>
That’s it! Your Liferay JSF portlet is upgraded and deployable to Liferay DXP 7.0!
You deploy a Liferay JSF portlet to Liferay DXP 7.0 the same way you deploy to
Portal 6.x. When the plugin WAR file lands in the
folder, Liferay DXP’s Plugin Compatibility Layer converts the WAR to a Web
Application Bundle (WAB) and installs the portlet as a WAB to Liferay DXP’s OSGi
On deploying an upgraded portlet, the server prints messages that indicate the following portlet status:
- WAR processing
- WAB startup
- Availability to users
Deploying a Liferay JSF portlet produces messages like these:
13:41:43,690 INFO ... [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:252] Processing com.liferay.faces.demo.jsf.applicant.portlet-1.0.war ... 13:42:03,522 INFO [fileinstall-C:/liferay-ce-portal-7.0-ga4/osgi/war][BundleStartStopLogger:35] STARTED com.liferay.faces.demo.jsf.applicant.portlet-1.0_4.1.0  ... 13:42:05,169 INFO [fileinstall-C:/liferay-ce-portal-7.0-ga4/osgi/war][PortletHotDeployListener:293] 1 portlet for com.liferay.faces.demo.jsf.applicant.portlet-1.0 is available for use
After the portlet deployment is complete, it’s available on Liferay DXP.
You’ve learned how to upgrade and deploy a Liferay JSF portlet. You resolved dependencies and deployed the portlet as you always have. It’s just that easy!