Fundamentals of Liferay Portlets - part 1

What is Liferay Portal?

  • Liferay Portal is the world's leading open source enterprise portal solution using the latest in Java and Web 2.0 technologies.
  • Runs on all major application servers & servlet containers,databases, and operating systems with over 700 deployment combinations.
  • JSR 168 and JSR 286 compliant
  • Out-of-the-box usability with over 60 portlets pre-bundled
  • Built-in Content Management System (CMS)
  • Built-in Collaboration suite
  • Personalized pages for all user

What are JSR 168 and JSR 286?
  • JSR 168 and JSR 286 are Portlet Specifications
  • They were created out of a need to have a specification for displaying multiple applications on the same page.
  • The specs define the lifecycle of a portlet as well as its characteristics/look and feel.
  • They standardize the way portlets are developed
What is a portlet?
  • A portlet is a web component that processes requests and generates dynamic content.
  • The content generated by a portlet is also called a fragment (e.g. HTML, XHTML, WML) and can be aggregated with other fragments to form a complete document.
Portlet Lifecycle
  • Portlets are different from servlets in that they have a 2 phase commit.
  • With servlets, the service() method processes all requests.
  • With portlets, the processAction() method processes the requests and the render() method draws the contents of the portlet on the page
Portlet Lifecycle
  • init() - Initializes the Portlet
  • processAction() - process input from a user action.
  • render() - Renders the content output.
  • destroy() - Cleans up the portlet
Additional methods of the lifecycle:
  • serveResource() - Allows a portlet to serve a resource. The serveResource() method can be used to implement AJAX use cases.
  • processEvent() - Perform events triggered by other portlets. (IPC)
Portlet Characteristics
  • Portlets have additional characteristics that make them different from Servlets
  • Portlet Modes
  • Window States
  • Portlet Preferences
Portlet Modes
  • Each portlet has a current mode, which indicates the function the portlet is performing.
  • All JSR 168 compliant portals should support the View, Edit and Help modes.
Window States
  • Window states indicate the amount of portal page space that will be assigned to a portlet.
  • All spec compliant portals should support the minimized, maximized and normal window states.
Portlet Preferences
  • Portlets can be configured to provide a custom view or behavior for different users.
  • For example, a weather portlet can show the temperature in Chicago for one user and the temperature in LA for another user.
  • These configurations are represented as a persistent set of name-value pairs and are referred to as portlet preferences.

You can have a quick overview of Liferay here 

Comments

Post a Comment

Popular posts from this blog

jQgrid reload with new data

To reload a jQGrid with fresh data you need to set the data parameter on the grid and invoke reload on it. jQuery("#promotionsGrid").setGridParam({ 'data': newData}).trigger("reloadGrid"); Here newData is a JavaScript array with which I need to re-load the grid. The important thing here is that I had to place this statement just before the grid initialization code even though the reload was expected on change event of a text box. Without that there was simply no effect on my grid!
Read more

Introduction to jQgrid

Introduction Why waste time in developing lists /customizing Liferay OOB search container to display data in tabular format. On top of that more often then not we end up coding for sorting of columns, pagination and formatting some data depending on their values. Trirand has come up with a jQuery plugin called jQgrid. jQgrid supports all of such ease. It provides a nice-looking grid with built-in features such as sorting, editing, search, drill-down, tree lists, and more. It is based upon jQuery and integrates well with Liferay.  The grid is dual-licensed under both the GPL and MIT licenses  (just like
Read more

Rich Client based UI technologies- A Comparison of Thick Client UI tools

Rich Client v/s Thin Client Software developers face many difficult decisions when building new applications, not the least of which is graphical user interface. There are various graphical user interface technologies used, but broadly they can be classified as Rich Client User interfaces and the thin client or web based user interfaces. To understand them better let us look at the history of rich and thin clients. While the Rich client GUI applications would support high quality end-user experience with features such a drag-and-drop, perspectives, customization, high speed local processing; it has had a traditional disadvantage of high deployment and upgrade costs. It was becoming highly difficult and costly to deploy and upgrade these applications. Then came the thin clients or the Web based applications. Thin clients solved many of the deployment and upgrade problems, but that was not without a cost, the cost was in terms of functionality and capability. Thin clients, based on...
Read more