liferay portal

Achieve remote access to the Liferay Portal 6.1 + Jboss PortalFire Cloud computing workgroup Deng qiusheng I. Problem DescriptionDownload Liferay Portal 6.1 + Jboss software bundle (http://sourceforge.net/projects/lportal/files/Liferay%20Portal/6.1.2%20GA3/

1, download liferay-portal-src-5.2.3 and liferay-portal-ext-5.2.3 2, build ext: In the Portal project Build.xml in turn to execute clean, start, build-ext tasks; 3, Portal and ext items are added under the App.server.zcb.propertie

Liferay is a complete portal solution, based on the Java EE application, using the EJB and JMS Technologies, the front interface part uses the Struts MVC framework, the XML-based portlet configuration file can be freely and dynamically extended, Web services are used to support the acquisition of some remote information, and the full-text search function is implemented using Lucene.The main features are as

Liferay provides a very simple method of Web application integration and single point of login: IFRAME Portlet. IFRAME Portlet can be used to easily include an existing web application, and form post or get can be used for user login. There is no problem with the liferay mechanism, and the implementation is also very clever. However, for many web application systems, after using the

Session Ii. the realization of Liferay Liferay when building Actionrequestimpl and Renderrequestimpl, a portlet session is set, as shown in the following code: public Renderrequestimpl ( HttpServletRequest req, Portlet portlet, cacheportlet cachePortlet, Portletcontext portletctx, WindowState WindowState, Portletmode portletmode, PortletPreferences Prefs, String layoutid) { ... _req = Dynamicreq;_portlet

From: http://www.theserverside.com/news/thread.tss? Thread_id = 39830 Liferay has released liferay portal 4.0, which brings a revamped fine-grained security model, enterprise taxonomy, delegated and cascading permissions and administration, public and private pages, JSR-170 compliance via jackrabbit integration, and page-level themes to the popular open-source

By default, the portletaction Extension Based on Struts action provided by liferay does not support multiple distribution commands, which are commonly used dispatchaction. However, in our daily Struts-based operations, a large number of dispatchaction processing methods have been used, such as "cmd = queryall. This article explains how to extend liferay to support multi-distribution command actions. First,

After the first login, liferay generates a default private homepage layout for the user. In earlier versions of liferay, you can configure the default group layout on the system administrator management interface. However, this function is not available in version 4.1, so by default, newly registered users first see the same private place content after login, these contents are provided by

Create a simple web project in myeclipse: (1) create a class under SRC and inherit from genericportlet. The Code is as follows: Package COM. portlet; (2) Create Table. jsp and the display. jsp codes are as follows: 1. Table. jsp: 2. display. jsp: (3) download the liferay-portal-tomcat-4.2.1.zip and decompress it to the F:/liferay/tomcat directory (this is

article source: www.idatafox.comSupporting Video library:Http://u.youku.com/javafacehttp://ke.qq.com/cgi-bin/courseDetail?course_id=83481Many sites are community-based, interactive, and you may have started using a separate forum, a wiki repository, or a chat program to achieve this goal, but let these standalone applications: forums, wiki repositories, or chat programs seamlessly interface to customers for a good cross-app experience, It is often difficult, fortunately, that

After several days of searching through the Liferay, the answers were found in the forums of the forum, hoping to help friends who are interested in deploying JPBM workflows in Liferay. 1. First download Liferay Portal Professional 4.2.1 (Bundled with Tomcat for JDK 5.0) 2, use its default Hsql database, that is, not

Release date:Updated on: Affected Systems:Liferay, Inc. Liferay Portal 6.1.1Description:--------------------------------------------------------------------------------Bugtraq id: 56589 Liferay Portal is a complete Portal solution. It is based on J2EE applications and uses

. Servicecomponentlocalserviceimpl.java is the core of the class, if you carefully study the code of this class will have other gains, here is only one example: you can see that this class actually supports the operation of upgrading the database, As long as the previous tablesql and the new TAblesql inconsistent, will perform the upgrade database operations, according to our thinking, we deployed two times the tables.sql is inconsistent, why not execute this code? Debugging finds that the Table

Iii. ProblemsDue to the above reasons, liferay may face the following problems:-The user originally wanted to save the private data to the session of the application, but actually saved it to the session object of the portal system.-Other applications can freely access session data that does not belong to this application.-Other systems can access the session data of the

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 portlet different Ications or among different user sessions.) The above passage is a section of the Portlet specification. As you can see, each portlet appli

Portal object 1. Request The request types in the portal are action request and render request. Therefore, the Portlet interface defines two methods to process different requests respectively. Processaction (actionrequest request, actionresponse response) and render (renderrequest request, renderresponse response) In a sense, the render method is similar to the service method in the servlet. The doview do

Remove the unused content from the Portal Settings page:In the/portal-master/portal-impl/src/portal.properties file, the following configuration is available:# # Input A list of sections that would be included as part of the company# settings form. #company. Settings.form.configu Ration=general,authentication,users,mail-host-names,email-notifications,content-shar

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 Portlet applications or among different user sessions .)The above section is a section in the Portlet specification. Clearly, we can see that each Portlet application should have

cas-server-3.5.2-release \ cas-server-3.5.2 \ cas-server-webapp directory find and open pom. xml, add the following before the first dependency, and compile Use the mvn install command to compile the war file, find the compiled war file in the following directory, copy and paste it to $ {liferay. home} \ webapps, and restart the Liferay server. If you do not have a Maven environment, or the compilati

Liferay version : Liferay-portal-6.1.1-ce-ga2 Server : Tomcat 7.0.25 Liferay is very large. The portal comes with dozens of Portlet, but you can choose to load the Portlet that comes with the portal as needed. Benefits: 1