Liferay is a Gartner Magic Quadrant Leader for the Sixth Year! Find out why

Portlet to Portlet Communication

Introduction #

The first version of the portlet specification, JSR-168/Portlet 1.0, did not include any support for Inter Portlet Communication. The second version, JSR-286/Portlet 2.0, has supported for IPC Mechanism.

JSR-286 makes it easy to share the data between two portlets. Using IPC mechanisms, we can share the data from ACTION to VIEW phase and VIEW-VIEW Phase.

There are 3 ways to share the data between 2 portlets.

  1. Portlet session
  2. IPC Mechanisms
    1. Public Render Parameters
    2. Event
    3. Client-Side IPC
  3. Cookies

1. Portlet Session #

By default, Each WAR has its own session and will not be shared with other WARs. Liferay provides a mechanism by which Portlets can share session attributes across WARs.

A PortletSession is created for each user per portlet application. This makes the PortletSession useful for communicating all user related information among different portlets in the same portal application.

Step 1: Set below attributes in Portlet1 #



Step 2: To set the Session #

    PortletSession session = renderRequest.getPortletSession();
    session.setAttribute("sessionValue", some-value ,PortletSession.APPLICATION_SCOPE);

Step 3: Get the Session Value in Portlet2 #

    PortletSession ps = renderRequest.getPortletSession();
    String tabNames = (String)ps.getAttribute("sessionValue ",PortletSession.APPLICATION_SCOPE);

2. Inter Portlet Communication (IPC) Mechanism #

2.1 Public-render-parameter Inter-portlet Communication #

 Illustration of IPC through public-render parameters

In JSR 168, the render parameters set in processAction is only available in the render of the same portlet. With the Public Render Parameters feature, the render parameters set in the processAction of one portlet will be available in render of other portlets also.

By adding the following property in portlet-ext, we can enable portlets to share render states with other portlets that are on different pages:


Step 1: Add below attribute in "Sender-Portlet" #

            <qname xmlns:x="">x:param1</qname>

Note:We can declare a list of public paramters for a portlet application.

Step 2 #

We can set render parameter in the processAction() method by using the defined public render parameter identifier as the key.

    response.setRenderParameter("id1", "someIdValue");


    public void processAction(ActionRequest  request, ActionResponse response) throws IOException, PortletException  {
        response.setRenderParameter("id1", “someIdValue”); ........

Step 3: Receiver Portlet Portlet "portlet.xml" #

Specify the render parameter the portlet would like to share in the portlet section.

            <portlet-name >PortletB< /portlet-name>
        </portlet >
            <qname xmlns:x="">x:param1</qname>

Step 4 #

A portlet can read public render parameter using following method request.getPublicParameterMap()

Note:Public render parameters are merged with regular parameters so can also be read using


Step 5 #

A portlet can remove a public render parameter by invoking following methods.


2.2 Event Inter-portlet Communication #

 Comic Illustration of IPC using Events

Portlet events that a portlet can receive and send.

In JSR-168 The only way to achieve eventing was through portlet session. The limitation of this approach was that the Portlets has to be in the same web application.

In JSR-286 JSR 286 (Portlet 2.0) defines a lifecycle for events, so that eventing is possible between portlets that are in different web applications.

By adding the following property in, we can enable portlets to send and receive events from other portlets that are on different pages


Step 1: Sender Portlet #


The portlet standard defines a way of telling the portlet container which portlet is responsible for sending an event.

Add this inside <portlet> tag:

            <supported-publishing-event xmlns:x=''>

        <event-definition xmlns:x=''>

Step 2: Set the event in process action #

    javax.xml.namespace.QName qName = new QName("", "empinfo", "x");
    response.setEvent(qName, "Hi! You have received Event Data sent from Sender Portlet");

Step 3: Listener Portlet #



            <supported-processing-event xmlns:x=''>
        <event-definition xmlns:x=''>

Step 4: get the EVENT #

This Event will be called after processAction as shown in the picture:

Lifecycle for IPC Event

 Lifecycle illustrated

    @javax.portlet.ProcessEvent(qname = "{}empinfo")
    public void handleProcessempinfoEvent(javax.portlet.EventRequest request, javax.portlet.EventResponse response) 
                throws javax.portlet.PortletException, {
        javax.portlet.Event event = request.getEvent();
        String value = (String) event.getValue();

        System.out.print("value in process event>>>>>>>>>" + value);
        response.setRenderParameter("empInfo", value);

2.3 Client-Side IPC #

There are 2 APIs for client side IPC.

Event generation (call from Portlet-A):
            '<eventName>', {
            name: value 

            'planTravel', {
            origin: 'pune',
            destination : 'mumbai'

Event Listener (call from Portlet-B):

            function(event) {
                // your code


            function(event) {
                showNews('', event.origin);
                showNews('', event.destination);

3. Cookies #

Other than the IPC mechanism, there is an easiest way to get the data between portlets on different pages through Cookies.

But there are some limitations for cookies:

  1. It will not accept more than 4KB size of data
  2. The biggest limitation is, the 20 cookies per server limit

and so it is not a good idea to use a different cookie for each variable that has to be saved.

Portlet 1 #

To Set the Cookies through jQuery:

    <script src="/html/js/jquery/cookie.js" type="text/javascript" > </script>
    function setCookie(docURL) {

To Set the Cookies through java/jsp:

    HttpServletResponse response = PortalUtil.getHttpServletResponse(actionResponse);
    Cookie cookieParam = new Cookie("cookieParam ", password);

Portlet 2 #

To get the Cookies through jQuery:

    jQuery.cookie("cookieParam ");

To get the Cookie through java/jsp:

    String sessionid = "";
    Cookie[] cookies = request.getCookies();
    if (cookies != null) {
        for (int i = 0; i < cookies.length; i++) {
            if (cookies[i].getName().equals("cookieParam ")) {
                sessionid = cookies[i].getValue();

- Gnaniyar Zubair

Children Pages

1 Attachment
Average (10 Votes)
The average rating is 4.5 stars out of 5.
Threaded Replies Author Date
Excellent Research Mr. ZUBAIR.... Thanks DarshanKumar N Bhatia November 30, 2010 2:58 AM
Thanks Darshan. Kowbathullah Gnaniyar November 30, 2010 5:06 AM
Awesome one Zubair bhai... :-) Raja Seth May 24, 2013 12:22 AM
nice summary! Thank you, Gnaniyar Zubair. Jonas Yuan November 30, 2010 3:00 PM
thanks Jonas. Kowbathullah Gnaniyar December 2, 2010 9:37 PM
nice post,thanks zubair Dhandapani S December 20, 2010 9:22 PM
Thanks dhandapani Kowbathullah Gnaniyar December 21, 2010 6:58 AM
Nice post. But can you please explain how that... Sandeep Nair February 7, 2011 4:32 AM
Thanks Jonas shahrokh hassanzadegan February 12, 2011 5:24 AM
Hello Zubair Shouldn't be in the fire portlet... Alexandru Ionita March 30, 2011 10:32 AM
Hi, But if I open two instances of the same... Ravi Polepeddi November 15, 2011 4:49 AM
Thanks! Suraj Bihari November 15, 2011 1:36 PM
@Alexandru Ionita: yes.. should be... ugandhar @ November 28, 2011 1:36 AM
Really nice work! A lot of thanks! Alejandro Santamaría January 16, 2012 1:03 AM
Hello Zubair, Excellent Bro!! Thanks for... Ashish Renapurkar July 7, 2012 1:19 AM
Thanks for such a nice & concise tutorial. Prakash Khanchandani July 26, 2012 3:57 AM
thanks for solution Friends Team October 30, 2012 11:12 PM
Hi, I'm trying to use the Liferay javascript... Jeroen Koek December 31, 2012 2:49 AM
Sorry guys, I solved it myself. Due to the... Jeroen Koek December 31, 2012 3:33 AM
Nice work.. Karthikeyan M March 14, 2013 10:14 PM
awesome :) useful post Mohammad Azharuddin December 18, 2013 8:31 AM
Very well explained! +1 Pankaj Kathiriya June 18, 2014 5:26 AM
Nice Post. Although I was following first... Hardik Pathak July 15, 2015 8:23 AM

Excellent Research Mr. ZUBAIR....
Posted on 11/30/10 2:58 AM.
Thanks Darshan.
Posted on 11/30/10 5:06 AM in reply to DarshanKumar N Bhatia.
nice summary! Thank you, Gnaniyar Zubair.
Posted on 11/30/10 3:00 PM.
thanks Jonas.
Posted on 12/2/10 9:37 PM in reply to Jonas X. Yuan.
nice post,thanks zubair
Posted on 12/20/10 9:22 PM.
Thanks dhandapani
Posted on 12/21/10 6:58 AM in reply to Dhandapani S.
Nice post. But can you please explain how that QName resolves namespace conflict in Public render parameter. In Eventing it is clear since we use qname to refer them in the lifecycle method. But in public render parameter we never make use of qname anywhere. We just use the identifier in Java as well as in supported public render parameter. How does qname actually resolve namespace issue for public render parameter?
Posted on 2/7/11 4:32 AM in reply to Gnaniyar Zubair.
Thanks Jonas
Posted on 2/12/11 5:24 AM.
Hello Zubair

Shouldn't be in the fire portlet the property <supported-publishing-event> instead of </supported-processing-event>. Otherwise you can't know which portlet is triggering and which portlet is listening.

Posted on 3/30/11 10:32 AM.

But if I open two instances of the same portlet in two browser tabs, how is one event different from the other ?
Posted on 11/15/11 4:49 AM in reply to Alexandru Ionita.
Posted on 11/15/11 1:36 PM.
@Alexandru Ionita: yes.. should be <supported-publishing-event> for Step 1: Sender Portlet
Posted on 11/28/11 1:36 AM in reply to Suraj Bihari.
Really nice work! A lot of thanks!
Posted on 1/16/12 1:03 AM in reply to Ugandhar Reddy.
Hello Zubair,

Excellent Bro!! Thanks for toooooooo informative article...

Regards n thanks ...
Posted on 7/7/12 1:19 AM.
Thanks for such a nice & concise tutorial.
Posted on 7/26/12 3:57 AM in reply to Ashish Renapurkar.
thanks for solution
Posted on 10/30/12 11:12 PM in reply to Prakash Khanchandani.
I'm trying to use the Liferay javascript api.
However this doesn't work when the user isn't logged on.
When I log on with a user the Liferay event bus is available but not when I'm not logged on.
Can you explain to me how I can enable this for the public (e.g. without a user logged on).
Thanks in advance.
Posted on 12/31/12 2:49 AM in reply to kumar g.
Sorry guys,
I solved it myself.

Due to the asynchronisation of the loading of the javascript some events where fired before I had registrated the Liveray.on.
To solve this you need to fire an event that is based on the PortletsAllReady event.

If that event arrives you can fire your own event to ensure that the listener is active to receive the events on load.

Hope this helps.
Posted on 12/31/12 3:33 AM in reply to J.P. Koek.
Posted on 3/14/13 10:14 PM.
Awesome one Zubair bhai... :-)
Posted on 5/24/13 12:22 AM in reply to DarshanKumar N Bhatia.
awesome emoticon useful post
Posted on 12/18/13 8:31 AM.
Very well explained! +1
Posted on 6/18/14 5:26 AM.
Nice Post. Although I was following first approach to share a parameter across two portlets within a same war, it seems that below line should be set in both source and destination portlet ( Above it's mention only in porlet1)


And after setting for both portlets it worked for me.
Hope this helps someone.
Posted on 7/15/15 8:23 AM.