Portlets are the most basic, most commonly used type of Liferay plugin you’ll develop. Think of your Liferay portal as a pizza crust (sit down, you can go order a real pizza later). Liferay comes with some basic toppings that make for a pretty good pizza out of the box (i.e., the core portlets and built-in functionality). Of course, your boss might demand anchovies, and Liferay definitely doesn’t come with anchovies. So what do you do? You take our tools, get some anchovies (your app’s source code), and integrate them with the pizza (Liferay). In these tutorials you’ll learn how to develop portlet projects to top your Liferay pizza in such a way that the end-user won’t be able to tell the difference between your custom portlet and Liferay’s core portlets.

In Liferay, you’re free to use any framework you prefer to develop your portlets, including Struts, Spring MVC, JSF, and Vaadin. Here you’ll use the Liferay MVC portlet framework, because it’s simple, lightweight, and easy to understand.

Related Topics

JSF Portlets with Liferay Faces

Creating a Liferay MVC Portlet Project

Portlets can be created in a Plugins SDK project or a Liferay Maven project. Liferay IDE lets you create either project type using command line tools: Ant in the Plugins SDK or Maven Archetype in...

Read More

Using Configurable Portlet Preferences

Portlet Preferences are properties for storing basic portlet configuration data. Administrators often use preferences to provide a customized view of a portlet to subsets of users or even all of a...

Read More

Using Portlet Namespacing

Namespacing ensures that a given portlet’s name is uniquely associated with elements in request parameters it sends to the portal. This prevents name conflicts with other elements on the portal...

Read More
0 (0 Votes)
Hot Deploy Versus Auto Deploy Previous