Basics of Portlets

        
          Portlet Life Cycle
  1. Initialization Phase :  init()                                                                                                       The portlet container intstantiate and initialize the portlet application.It call the init() method      for initial portlet configuration.
      2.  Action Phase         :  processAction() 
           When user request for a portlet action by hitting the ActionURL the processAction()
           method is called by the portlet container

      3.  Render Phase         :  render()
           Render phase is called automatically after the action phase is executed. if action phase of
           one portlet in a page is executed then render phase of all the portlet in that page is
           executed

       4. End of service Phase : destroy()


         Portlet URL 

  • renderURL: this is the type of URL that we have used so far. It invokes a portlet using only its render phase.
  • actionURL: this type of URL tells the portlet that it should execute its action phase before rendering all the portlets in the page.
  • resourceURL: this type of URL can be used to retrieve images, XML, JSON or any other type of resource. It is often used to generate images or other media types dynamically. It is very useful also to make AJAX requests to the server. The key difference of this URL type in comparison to the other two is that the portlet has full control of the data that will be sent in response.                                                                                                                                             

    PortletContext, PorteltConfig  and PortletPreferences

    PortletContext :-  PortletContext scope is application level which is used to access the values declared in the web.xml. It is accessible by the PortletContext.getInitParameter() method. PortletConext is accessible to all the portlets in that portlet application.

    PortletConfig :- PortletConfig is same as that of ServletConfig which is used to access the
    parameter declared in the portlet.xml file. PortletConfig is specific to a particular portlet
    and are accessible to all the instances of that portlet .

    PortletConfig.getInitParameter(""); 

    PortletPreferences : 
    Portlet preferences are user specific. A PortletPreference keeps information about a specific user.



     

Comments

Post a Comment

Popular posts from this blog

React development in Liferay - Overview

Image
Liferay is one of the leading opensource digital experience platform based on Java. On the other hand React is  the most popular and widely used java script framework currently available in the market.  With the release of Lifeay DXP platform we can create pure javascript based portlet in Liferay. This feature enable us to run single page application created using (React/Angular/ Vue) in Liferay DXP platform which allow developer to take advantages of both Liferay and SPA platform. This article explain about the things we consider and challenges faced during React portlet development in Liferay. SPA vs Portal Architecture A Portal is designed to have number of pages and child pages under a site and provide option to add multiple application in a single page. SPA have a completely opposite approach compared to Portal, SPA application have only single page which accommodate all your functionality. When we design a Liferay Portal application with SPA this is the first challenge ...
Read more

Deploy Liferay DXP on google cloud

Image
  In this article we will see how to deploy a Liferay DXP cluster in google cloud platform. The reference architecture will look like below. Here I have created a global https load balancer which will distribute the traffic to 2 liferay node in the cluster. I have created an unmanaged instance group for this purpose. I have created 2 Compute engine virtual machine for deploying Liferay DXP. We have used cloud SQL service from gcloud for Liferay schema. Filestore service used for document repository and a separate virtual machine with elastic search installed used as an elastic server.                                                                                                    ...
Read more

Liferay React with Webpack

Image
  Liferay is using its own bundler called Liferay NPM bundler for the normal build process. This article explains the challenges we faced while developing react portlet with liferay-npm-bundler and how to overcome those using a webpack build.   Why Liferay using its own bundler (liferay-npm-bundler)  Multiple Portlets can be added in a page In a Portal page we can add multiple application/portlets, The normal bundler like webpack will fail in this case since its designed to have one application in a page. Liferay NPM bundler is designed to support the following features. Reuse common module across the page   When you have multiple portlets in a page and all this portlet using some common module, liferay npm bundler will allow to load only one common module in the page and share it among the portlets. Avoid common module conflict   Use different version of same module in a page :  It allow you to use 2 version of the same module in a page OSGI modular a...
Read more