5/18/2023 0 Comments Web xml icefacesThis 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. ![]()
0 Comments
Leave a Reply. |