What is the difference between JSR 168 and JSR 286?

In JSR 168 (Portlet 1.0), the only way to achieve eventing between portlets was through a portlet session. This was possible between portlets that are in the same web application. JSR 286 (Portlet 2.0) defines a lifecycle for events, so that eventing is possible between portlets that are in different web applications.

Table of Contents

What is JSR in Liferay?

Roles in Liferay DXP are the primary means for granting or restricting access to content. If you’ve decided not to use Liferay’s permissions system, you can use the basic system offered by the JSR 168, 286, and 362 specifications that map Roles in a portlet to Roles provided by the portal.

How many portlet life cycle methods given by JSR 168 and what are they?

There are 2 JSR standards for portlet behavior: JSR 168 (Portlet 1.0 specification): Focuses on displaying multiple applications on the same page. It introduces the basic portlet programming model to support the MVC pattern , portlet modes, window states.

What is portlet in liferay?

Web apps in Liferay DXP are called portlets. Like many web apps, portlets process requests and generate responses. In the response, the portlet returns content (e.g. HTML, XHTML) for display in browsers.

What is meant by portlet?

a piece of software that is displayed in a portal (= a website or page on the internet that allows people, especially a group of people who are interested in a particular subject, to get useful information and to find other websites): This portlet can be added to a page by any user with the appropriate privileges.

Is Liferay DXP open source?

Liferay DXP is both Open Source and built in the open, following a collaborative development model.

What are the different portlet life cycles?

portlet have similar lifecycle as that of a servlet, portlet needs a portlet container similar to a servlet, we know that servlet have lifecycle of init(), service() and destroy() similarly liferay’s lifecycle have the following stages.

What are the two types of rendering portlets?

There are two types of portlet requests—action requests and render requests.

What is the use of portlet?

Portlets are reusable web modules that provide access to Web-based content, applications, and other resources. Portlets can run on the application server because it has an embedded JSR 286 Portlet container.

Is Liferay Java based?

Liferay is an open source enterprise portal used to enable corporate intranet and extranet. This Java-based web application platform provides a toolset for the development of customizable portals and websites.

What is portlet in web?

Is Liferay free?

This library, Liferay Portal Community Edition, is free software (“Licensed Software”); you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

JSR 286 is advanced portlet specification and it was added new features to JSR 168. We can also call Portlet Specification 2.0. Java Community People was founf some of the limitations in JSR 168 and they are added new specifications to JSR 168 then they released as JSR 286 standards. We already know JSR 168 standard and Portlet Specification 1.0

What is Liferay MVC portlet?

Liferay MVC Portlet Development with Liferay IDE Introduction: Liferay MVC is portlet development framework given by Liferay. We will use Liferay MVC framework to develop JSR 168&… Liferay Site/Organization Virtual Hosting

What are the JSR standards for portlet behavior?

There are 2 JSR standards for portlet behavior: Focuses on displaying multiple applications on the same page. It introduces the basic portlet programming model to support the MVC pattern , portlet modes, window states Init: The init () method is called by the portlet container during deployment and reads init parameters defined in portlet.xml file.

What is your experience with Liferay?

Some of us on the team have experience with Liferay, and we have pretty negative feelings about it. Dealing with things like full-page refreshes, portlet lifecycles, style and theming issues, and limited DBMS coverage are at the top of our list of complaints. We see where our executive team is coming from.