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.
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.
#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. These are used by the CustomerController managed bean.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. * Two utility classes ( JsfUtil and PaginationHelper) residing in the my.org.ui.util package. * A JSF session-scoped, managed bean named CustomerController, that resides in the my.org.ui package. * Bundle.properties: A properties bundle that contains default localized messages for the JSF views. This class can equally be accessed from the project’s Enterprise Beans node. * A stateless session (enterprise) bean named CustomerFacade, that resides in the my.org.data package. * template.xhtml: An optional Facelets template page, which includes a reference to the generated jsfcrud.css stylesheet. * jsfcrud.css: A stylesheet used to render the JSF forms and data table. * View.xhtml: A JSF form for viewing customer details. * List.xhtml: A JSF data table for scrolling through customers. * Edit.xhtml: A JSF form for editing a customer. * Create.xhtml: A JSF form for creating a new customer. * A customer folder in your web root, that contains four Facelets files for CRUD capabilities: For example, specifying /my/org/Bundle for Localization Bundle Name in the wizard generates the following entry:
* A faces-config.xml file to register the location of the properties bundle that contains localized messages for the JSF views. For example, if you are applying the wizard to a Customer entity class, the settings shown in the image above will generate the following files:
0 kommentar(er)
