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 organization# form when adding an organization. #organ Izations.form.add.main=details,organization-siteorganizations.form.add.identification= Organizations.form.add.miscellaneous=# Input A list of sections that'll be included as part of the Organizatio n# form when updating a organization. #organizations. Form.update.main=detail
22:00:39,557 ERROR [schedulermessagelistener:53] Unable to process message {destinationname=liferay/scheduler_engine, Responsedestinationname=null, Responseid=null, payload= COM.LIFERAY.PORTAL.KERNEL.SCHEDULER.MESSAGING.SCHEDULERREQUEST@D870CB, Values=null}
Com.liferay.portal.kernel.scheduler.SchedulerException:Unable to start Scheduler
At Com.liferay.portal.scheduler.quartz.QuartzSchedulerEngineImpl.start (quartzschedulerengineimpl.java:276)
At Com.l
This problem actually stuck me for 1 hours, mainly beginning to think complex.
Because the default if the site to do in-station navigation, we are implemented with JS, and Liferay page is so complex, because the portal page is composed of a portlet, each page ID composition is also very complex, so I have been doing it for a long time did not get out, Until I returned to the basic definition of portal.
In the portal definition, a very important feat
Liferay has a service builder mechanism that generates a set of interfaces and classes and configuration files for the persistence Layer and service layer, and when we write a service.xml and invoke ant target as Build-service, The framework uses the Servicebuilder class to parse the Service.xml file:
For example, the service.xml we create is:
When we run Build-service Target, the location of this service.xml file is used with the first paramete
In the/portal-master/portal-web/docroot/html/portlet/dockbar/add_panel.jsp fileThe following will be included:if (hasaddcontentandapplicationspermission) { "content,applications");} if (haslayoutaddpermission) { "page");}Modified to:if (hasaddcontentandapplicationspermission) { "applications");} if (haslayoutaddpermission) { "page");}Remove the following content:"/html/portlet/dockbar/add_ content.jsp" /> Liferay 6.2 Retrofit Series Three
1. A single JSP file is directly suffixed with. jsp; a JSP file containing multiple JSP files is suffixed with. jspf.
2. Use single quotes in JS files
Confirm ('
3. Use the field set to wrap the input box
4. Use the built-in liferay Separator
1. Cancel the display of the above dockbar
This is the default code in the liferay topic, that is, all login users will display this control bar.
Dockbar is the top column.
#if ($is_signed_in) #dockbar()#end
Change to the following:
#if (($is_signed_in) $permissionChecker.isCompanyAdmin($company_id)) #dockbar()#end
Non-admin users will not be displayed
Ii. Access prohibited
You can still access the Control Panel through this connection:
Http: // lo
Now let's make a summary:
In fact, in order to have a better user experience, we have optimized from all aspects:
The resource itself is cropped in size:
For CSS,JS resources, we compress them with yui-compressor.
For image resources, we use the Sprite tool bar multiple small pictures merged into large single pictures
The cost of resources being downloaded from the server to the client is reduced:
We have enabled the filtering of gzip filter on the server so that all the resources are comp
In Liferay, if we want to use our own JS library (such as the EXT-JS Library) instead of the default AUI library, you can follow these steps:
(1) Place the library file
We go to the $liferay_home/tomcat-7.0.23/webapps/root/html/js directory to build a directory called ExtJS, and then copy ext-all.js into.
(2) Create the portal-ext.properties in the $liferay_home directory and then from the portal.properties in the Portal-impl.jar package Javascri
The Liferay SDK has the following directory structure:
clients/is the directory for the client plug-in and provides an ant script to create the client plug-in
dist/This directory holds the archive applications for deployment and release. For example, the last time we wrote 2 portlets, here are 2 corresponding applications:
ext/is the directory of the Ext plugin and provides an ant script to create the EXT plug-in
hooks/is the directory of the
DockBar is the most active element in Liferay, because almost all of the user's operations start from the DockBar, so we're here to analyze the DockBar in depth.
Structure of the DockBar:
DockBar is divided into 2 parts from the whole, part is the left
The other part is the right
So the final DockBar structure is (I omitted a lot of code):
Conclusion:
Theme Upload logo will do the following things:
(1) Using Uploadportletrequest object to handle the
(2) for the uploaded logo picture is empty, then throw an exception.
(3) for the upload of the logo picture is not empty, the first from the database to find the current layout, for logo definition logoid, and bar logoid add to the current layout and then back to the database, and then set according to the Boolean variable to determine whether it is the logo associated to the hook
After learning the ant build theme, Liferay theme, we easily ported the theme project to Maven. The following are the specific steps:
Assume:
Because we used the http://supercharles888.blog.51cto.com/609344/890525 development structure as shown in the article, let's assume we put the theme we're developing in D:\WalmartProject.
First: Let's use the Maven Theme Wizard to create a theme:
Once created, because we want our pom.xml to inherit Father
. 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
Today I looked at JBoss Boot.log and Server.log logs, combined with their own understanding and other information, and now the launch and loading process of JBoss to make the following summary;
This article takes the JBoss application Server 4.2.1 GA (hereinafter referred to as JBoss) as an example to introduce its sta
Today I looked at JBoss Boot.log and Server.log logs, combined with their own understanding and other information, and now the launch and loading process of JBoss to make the following summary;
Boot.xml is a log of the server's startup process and does not involve subsequent procedures
Server.xml is a log of the operation process and is more detailed, which contains the process of initiating
This a
The first step is to check if disk space is insufficient, and the second step is to check if the Jboss-log4j.xml configuration information in JBoss is changed This is the detailed configuration information for jboss-log4j.xml inside JBoss: http://my.oschina.net/liangbo/blog/215593 is not, then the information obtained
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.