Thanks Deepak.

I made the checks and it seems OK. By seeing different changes in my portlet behaviour I can see that Open Portal porlet container implementation is chosen. The test on caching are OK now (previously, I was misinterpreting the results).

However, I have two annoying side effects with the Open Portal's implementation, compared to the Liferay's:

1) 'portletSession' variable is no longer defined in the JSP. As a workaround I added the following statement in all my JSPs:

<%@page import="javax.portlet.PortletSession"%>
<%PortletSession portletSession = renderRequest.getPortletSession();
%>

This is OK, except that I cannot switch easily between the two portlet container implementations : when I switch back to the Liferay implementation, I get a 'duplicate variable' error.


2) The emitting of event (in the JSR-286 sense) through setEvent call in my portlet Java code does not work. It throws an exception.

public void processAction(ActionRequest req, ActionResponse res)
throws IOException, PortletException {
...
res.setEvent(newResultsEventQName, result);
...
}
With the Liferay implementation, this was perfectly all right. I made the check several times with both implementation to be sure.

Do you have explanations on these two issues ?