Thanks for your suggestions, Oliver.
I succefully checked that Liferay assign a unique ID to each instance of the portlet.
I also noticed that when a portlet instance changed its mode all the portal page was reloaded: this caused all other portlet instances to be reloaded. This happened because the URL of the portal page changes in order to reflect the portlet instance mode change.
I would like to know if the whole portal page is loaded because of the way I handle portlet mode. Below you can find the code of the Portlet class I defined:
public class TestMultiplePortlet extends GenericPortlet {
public void doView(RenderRequest request, RenderResponse response)
throws PortletException, IOException {
System.out.println("VIEW " + request.getWindowID());
response.setContentType("text/html");
PortletRequestDispatcher dispatcher =
getPortletContext().getRequestDispatcher("/WEB-INF/jsp/TestMultiplePortlet_view.jsp");
dispatcher.include(request, response);
}
public void doEdit(RenderRequest request, RenderResponse response)
throws PortletException, IOException {
System.out.println("EDIT " + request.getWindowID());
response.setContentType("text/html");
PortletRequestDispatcher dispatcher =
getPortletContext().getRequestDispatcher("/WEB-INF/jsp/TestMultiplePortlet_edit.jsp");
dispatcher.include(request, response);
}
public void doHelp(RenderRequest request, RenderResponse response)
throws PortletException, IOException {
System.out.println("HELP " + request.getWindowID());
response.setContentType("text/html");
PortletRequestDispatcher dispatcher =
getPortletContext().getRequestDispatcher("/WEB-INF/jsp/TestMultiplePortlet_help.jsp");
dispatcher.include(request, response);
}
}
As you can see, every change in portlet mode causes a dispatching to a specific JSP that provides some HTML tags. Could this dispatching be the cause of the reload of the entire page? In general, is this a "normal" behaviour?
I enclosed a ZIP archive (testMultiplePortlets.zip) which contains the Eclipse Helios Project I used to define the portlet.
