liferay portlet

Introduction: Debugging analysis: In fact, according to. From the conclusion above, we know that web. xml is added with a lot of additional content and then split into 2 files, 1 is the portal-web.xml file, which contains all the definitions of the filters except (Invoker Filter, the other is web. xml, it adds a lot of content, andMost importantly, it adds a PortletServlet definition in web. xml. Therefore, go to the webapps on the server and check the web. xml in the Application Deployment

Introduction: Deploying a portlet in Liferay is far simpler than deploying a web application to tomcat. This article shows the secrets of this deployment. For example, when we drop a war package of logsearchportlet in $ LIFERAY_HOME/deploy: 650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/15463531P-0.png "title =" 21.png"/> Analysis: After this action occurs, it will be captured by

Session One, the description of the session in the specification (Portletsession objects must is scoped at the Portlet, application the context level.) Each portlet application has its own distinct the Portletsession object per user session. The Portlet container must not share the Portletsession object or the attributes stored in it among

Introduction: The project team asked me if A Portlet has multiple modes, for example, a previously developed portlet has both the view mode and the config mode), and the front-end uses the extjs mvc Architecture, and the main file is main. js, the main. js is defined in liferay-portlet.xml with the following 650) this. width = 650; "src =" http://www.bkjia.com/u

", "Com.liferay.portlet.maximize-help", "Com.liferay." Portlet.parent-struts-path "," Com.liferay.portlet.pop-up-print "," Com.liferay.portlet.preferences-co Mpany-wide "," Com.liferay.portlet.preferences-owned-by-group "," Com.liferay.portlet.preferences-uniq Ue-per-layout "," Com.liferay.portlet.private-request-attributes "," Com.liferay.portlet.private-sessi On-attributes "," com.liferay.portlet.remoteable "," Com.liferay.portlet.render-timeout "," Com.liferay.portlet.render-weight "," Com.li

Liferay by default in the case of Tomcat, jetty and other servers, automatically install the Marketplace-portlet-6.2.0.1.war package, implement automatic deployment of the store, generally do not need the store, so delete the following package:/portal-master/portal-impl/src/com/liferay/portal/deploy/dependencies/plugins1/marketplace-

Original: http://blog.csdn.net/hantiannan/article/details/7311845 In the Menu Add button, list the portlet. But in many cases our site uses only a subset of the content. How to hide some unwanted portlets. There are two ways of doing this: The first is to modify the configuration file: Portal-web/docroot/web-inf/liferay-display.xml Put what you don't need in the Category.hidden. Your own

When we use to build a Nexus local warehouse, and configure Settings.xml to enable this repository for applications. We use the archetype of Liferay 6.1.10 to create the Liferay portlet, as shown in the following figure: When we run the command MVN package Liferay:deploy, the following error occurs: 01.[debug] Using connector Wagonrepositoryconnector with pri

1. Session Description in the Specification (Portletsession objects must be scoped at the Portlet application context level. each Portlet application has its own distinct portletsession object per user session. the Portlet container must not share the portletsession object or the attributes stored in it among different Portle