Some time we may face problem of creating Liferay plugin applicat ion with liferay-plugins-sdk-6.2-ce-ga3 with Liferay IDE 2.x due to incomplete download of ivy required jar files and configuration files through eclipse.When we trying to create Liferay plugin project for first time, the project may not be created successfully due to problem with downloading of ivy related required jar files from eclipse.In Liferay plugins sdk 6.2 GA3, we can find .ivy directory (liferay-plugins-sdk-6.2\.ivy). In side of .ivy directory we can see cache directory and ivy-2.3.0.jar file.

Due to some proxy issues or fire wall problems or internet connectivity, the ivy related all jar files and other configuration files will not be downloaded in the cache (liferay-plugins-sdk-6.2\.ivy\cache) directory for first time when we create Liferay plugin project. For the first time if everything is fine then it will take several minutes to download all required jar files and configuration files in plugins-sdk cache location (liferay-plugins-sdk-6.2\.ivy\cache). In some cases the creation of new Liferay plugin project may not be completed and keep on loading like shown in below screenshot, then there might be a problem with down loading of ivy related jar file. In that case we need to download all .ivy related jar files manually.

Liferay Hooks are used to customize the liferay portal. We have many kinds of hook plugins one of the hook is Portal Properties hook. Introduction to Liferay Hook Plugins Portal properties hook overriding the existing portal properties and Portal properties hook can modify the some of the portal properties not all the portal properties. The modifiable list of properties are specified in liferay-hook_6_x_x.dtd file. If the properties are not listen in the liferay-hook_6_x_x.dtd file then we cannot modify it from portal properties hooks. Assume we want to modify login.events.pre ,login.events.post properties then we will use Portal Properties Hooks. If the portal properties are not listed in above then its not possible to override from portal properties hook plugins then we have to use portal-ext.properties file.

Existed Behavior of Liferay portal Create Account Page In the liferay portal create account page we cannot find password field that user can create his own password at the time of registration. After registration user will get mail with auto generated password to login into portal and then he/she can change the password from his/her my account page password section.

Liferay hook Plugin is one of the Plugin type in liferay to customize liferay portal. Hook have many capabilities so that we can customize liferay portal and its hot deployable plugins. Liferay Plugins SDK have support to develop hook plugins. Please follow the articles before start this development. Introductionto Liferay Hook Plugins Liferay Development Introduction We have many choices to start liferay development LiferayIDE Liferay Plugins SDK+ANT Liferay Development with MAVEN In this article we are going to see hook development with Liferay IDE. Before start development we need to be ready with development environment that is using Liferay

Deployment of Hook Plugin As soon as we created hook project then respective build file will be appeared in the Eclipse ANT view. There we can see many ANT targets. Simply we have to double click on deploy target or we can simply double click on Project Name in the ANT view then it will execute deploy target then hook Plugin will be deployed into server. deploy is the default ant target for hook Plugin.

Some time we may get requirement to access liferay portal live users/logged in users information in Plugin portlets. Generally Liferay have implemented class called “LiveUsers.java” class in the portal level which is not available in Plugin environment. LiveUsers.java is class which contains set of methods from this we can get logged in users/portal live users information. Problem: LiveUsers.java implemented in portal level so which is not directly available in Plugin portlet environment.

Solution: We will use portal class loader to load LiveUsers class and we will use Java Reflection Mechanism to call methods from LiveUsers.java What is portal Live Users? Portal Live users are the logged in users they are currently live in the portal. Access Portal Live Users in Plugin Portlet Environment Add “live.users.enabled=true” property in portal-ext.properties file Use Portal Class Loader and Java Reflection API to access methods in LiveUsers.java Add “live.users.enabled=true” property in portal-ext.properties file Generally live.users.enabled property set as “false” in portal.properties file . If we want to know portal live users information we need to make that value as “true” this property value overridden through the portal-ext.properties file which in Liferay Home directory

Introduction: Liferay have come up with their portlet frame work called Liferay MVC. Liferay MVC is portlet development framework and we can develop JSR 168 and 286 standards portlets and deploy into Liferay Portal. Liferay MVC is portlet framework specially designed for liferay and we can develop portlet and deploy into liferay portal. This frame work has many features and it uses Liferay APIs to rapid portlet development and easy to use. It is very light weight frame work and it come up with liferay Plugins SDK. Liferay MVC portlet is default liferay portlet development frame work and it is inbuilt in Liferay Plugins SDK. We need not to do any additional configuration or need not to add any additional jar files when we develop portlet using Liferay MVC. It’s also follows all JSR portlet standards and it inherited the Generic Portlet features.

Liferay IDE has support to create Liferay MVC portlet and deploy into servers. Generally when we use Generic Portlet developer need to handle more code but when we use Liferay MVC it will cut down development effort when we think in prospective of code, it have very good mechanism to handle portlet lifecycle..

Introduction: Liferay is huge web portal consists of many things which make ready to use web application in real time. In the theoretical way liferay consist of following building blocks which will run the entire liferay portal. Site Organization Users Group Roles and Teams Users Permissions Site: Liferay have concept called site, in general site is like website which consist of pages, web content , users and some dynamic functionality, we can say sites are used to organize pages, content, application data. In general business scenario we will display our information through website in the internet and we will use some html or some other web application technology to achieve it.

To make this liferay have different artifacts like pages, web content and some dynamic applications called portlet, all together will make website or site. For each site we have different stake holders or end users to access the site, in the same way liferay have users and we can assign users to particular site so that they will surf around the web site. In the site we will have site pages and each page have certain layout and each page consist of some static content and dynamic content. In liferay we will use Web content management system to design content for site and we will use portlet application to meet dynamic functionality.