#JSF ICEFACES DEVELOPED BY CODE#

The init-param is also defined here, which ensures your portlet is visible Liferay Faces Bridge, easy to develop by acting as a turnkey implementation. Invocations to your JSF portlet and makes your portlet, since it relies on For example, itĭescribes portlet info, security settings, etc. The portlet.xmlĭescriptor describes the portlet to the portlet container. Modify your webapp/WEB-INF/portlet.xml as desired. This is required to initialize JSF and should be defined in all JSF portlets Make sure the Faces Servlet is configured in your web.xml: Provides necessary configurations for your JSF portlet to deploy and The web.xml file serves as a deployment descriptor that Replace your new JSF portlet’s webapp/WEB-INF/web.xml with your web app’s Portlet’s application configuration file, which is used to register and Replace your new JSF portlet’s webapp/WEB-INF/faces-config.xml with your

Log4j.properties file in the src/main/resources folder sets propertiesįor the Log4j logging utility defined in your JSF portlet (i.e., Portlet’s portlet.xml file, and from Liferay DXP’s Language.propertiesĬonfigure your portlet’s logging configuration as desired. Object can access messages both from a resource bundle defined in the Using the implicit i18n object provided by Liferay Faces Util. In the i18n.properties file can be accessed via the Expression Language ForĮxample, your web app’s CSS files would reside in theĪdd your image files to the webapp/resources/images folder.Īdd localized messages to the resources/i18n.properties file.

Runtime group: '', name: '.impl', version: '4.1.3'Ĭopy your Java classes to the new java// folder.Ĭopy your view templates to the new src/main/webapp/WEBINF/views folder.Īdd your frontend files (e.g., CSS, JS, etc.) that shouldn’t be accessedĭirectly by the browser to the webapp/WEB-INF/resources/ folder. The required artifacts required to deploy a simple JSF portlet to Liferay DXP. web.xml → Web application configuration.liferay-portlet.xml → Liferay-specific portlet.liferay-plugin-package.properties → Packaging.resources/ Frontend files (e.g., CSS, JS, XHTML,Įtc.) that shouldn’t be accessed directly by the.log4j.properties → Log4J logging configuration.resources/ → Resources to include in the class path.dto/ → Sub-package for model (data transfer.bean/ → Sub-package for managed Java beans.Here’s the resulting project structure for a JSF Standard portlet: The above archetypes support both Gradle and Maven development by providingĪ adle and pom.xml, respectively. .richfaces.portlet (Liferay RichFacesĬhoose the archetype that matches your web app’s JSF component suite..primefaces.portlet (Liferay PrimeFaces..icefaces.portlet (Liferay ICEFaces portlet)..butterfaces.portlet (Liferay ButterFaces..bootsfaces.portlet (Liferay BootsFaces..alloy.portlet (Liferay Faces Alloy portlet).You can deploy your new JSF portlet project to Liferay DXP.Ĭreate a new JSF portlet project.

#JSF ICEFACES DEVELOPED BY CODE#

Generating a new Liferay JSF Portlet project and migrating your code to it. You must also provide portlet-specific descriptor files to make itĬompatible with the Liferay DXP platform. To run an existing JSF web app on Liferay DXP, you must leverage the Liferay FacesĮnables you to deploy JSF web apps as portlets without writing portlet-specificĬode.

Jsf icefaces developed by