liferay support

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

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. Improved startup speed (performance) 2. The interface can be more concise. After all, no Portlet is needed. Look at Xuan Hu, it's

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 compilation fails, you can find the cas-server-3.5.2-release directly in

jar package: 650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/1545325127-13.png "title =" 55.png"/> First, it first determines the server type, because we are tomcat, so it will go to all the jar packages in tomcatLibDir in the exclusion list, this tomcatLibDir is 650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/154532F10-14.png "title =" 56.png"/> Then it will read conext. xml. If com. liferay.

Liferay has released version 4.1.0. The newest version provided des a message board and Web 2.0-style mail Portlet, Geronimo support, and improved LDAP integration. Now in its sixth year of development, liferay is JSR-168 compliant and runs on almost any major application server, database, and operating system, rendering over 700 deployment combinations. Additio

can search for hibernate within portal.properties. Found.Data sources that let Liferay use the middlewareSometimes we don't want to use a JDBC connection pool to manage our database connections, and we want to use middleware data sources, such as Tomcat's data sources, WebLogic data sources. At this point we only need to add the following configuration in Portla-ext.properties or portal-setup-wizard.properties Jdbc.default.jndi.name=jdbc/liferaypool

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.properties file, the file name "ZCB" for the computer's login, as follows: Lp.ext.dir=f://eclipse_project//liferay b-

Because our application is running on the Liferay application server, some optimizations for the server are of course our first thought. We have done a lot of testing before, because Liferay will have css-fast-load, and js-fast-load, these parameters will be a number of CSS files or several JS files merged into a single large file, which can significantly reduce the number of network IO overhead, We develo

portal. that# happens by because the counter service would look up the properties# prefixed with "jdbc.default." To create its data Source. See the jdbc# properties prefixed with "Jdbc.default." For more information.## Setting a different value for the counter J DBC prefix allows better# fine tune the counter data source with its own set of configuration# settings for high AV Ailability installations. Note that these settings,# though separate, is a copy of the default settings with the newly#

management (cms,jsr170) Portal-service Includes all service interfaces for Portal-impl Portal-kernel Includes the Portal/portlet specification implementation (JSR 168/268), as well as basic framework management (Struts, Spring), and basic implementations of deployment, configuration, Search, WebService, and persistence Support-glassfish/tomcat Support implementation for GSF/TOMCAT container Util-bridges

Liferay has two types of services: 1) Internal ServicesLiferay core services, such as portal-impl.jar 2) External ServicesThat is, portal APIs, such as portal-kernel.jar and portal-service.jar The liferay internal service is updated frequently. Pay special attention to the liferay version upgrade. The liferay external

After the Portlet is deployed, an exception is reported-cocould not initialize class com. liferay. util. Portlet. portletprops. Briefly describe the Portlet. properties. During the development of the Portlet, you can customize the configuration file-Portlet. properties similar to portal. properties. The procedure is as follows: 1. Create the Portlet. properties in classpath, such as the WEB-INF/src directory line.chart.types=line,spline,column,bar,t

Last time, in this blog http://supercharles888.blog.51cto.com/609344/897825, We're talking about how to fix the multiple dependencies on slf4j that arise when using Maven's Service-builder, and now we're going to show you how to customize the plugin. This allows you to avoid this error by using our own plug-ins instead of the default Liferay-maven-plugin in your project: Authoring of Plug-ins: Specific writing details will not say, anyway, is to use

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

The following is a typical startup process for Liferay server: 01.May 3:09:32 AM Org.apache.catalina.core.AprLifecycleListener Init02.info:the APR based Apache Tomcat Native Library which allows optimal performance in production environments is not fo und on the Java.library.path:d:\charles\softwares\java\jdk1.6.0_05\bin;03.May 3:09:34 AM org.apache.coyote.AbstractProtocol Init04.info:initializing Protocolhandler ["http-bio-8080"]05.May 3:09:34 AM or

. registerbeanpostprocessors (abstractapplicationcontext. Java: 710) At org. springframework. Context. Support. abstractapplicationcontext. Refresh (abstractapplicationcontext. Java: 410) At org. springframework. Web. Context. contextloader. createwebapplicationcontext (contextloader. Java: 282) At org. springframework. Web. Context. contextloader. initwebapplicationcontext (contextloader. Java: 204) At org. springframework. Web. Context. contextloade

Document directory I. Custom Fields 2. Monitoring) Iii. Plug-in configuration 4. Page Template 5. website template Vi. Server Management VII. Portal instances 8. Plug-in Installation IX. Summary I. Custom Fields Custom fields are a method of adding attributes to many types of sets in a portal. For example, if you use liferay to create a book rating site, you can add custom fields to many collections in the portal. For example, you can add

When we create Liferay applications (such as Portlet,theme) with Maven, we often have a version choice, as shown in the figure: The default show's last version of Archetype is selected, at which point we can only display the latest version of archetype, if we use the latest version of archetype development application, then eventually when the application deployed to the lower version of the container ( For example, the

Liferay 5.1.1 Installation and Integration CAs Reprint please retain the author information: Author: 88250 blog:http:/blog.csdn.net/dl88250 MSN Gmail qq:dl88250@gmail.com Directory Summary 1 Environment 1 Download liferay 5.1.1 2 Configuration Database 2 Configuration Data Source 2 Build Database 2 Create DATABASE User 2 Add Database Connection Driver 2 Test Login 3 Consolidating CAS 3 Configuring CAS Se