Portlet 3.0 TCK: Fix session invalidation logic

• Type: Technical Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.0.0 DXP FP35, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, Master
• Component/s: None
• Labels:
  • liferay-digital-enterprise-70-sp7
  • liferay-fixpack-de-35-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/54031

Test failures:

6 session invalidation related test cases fail:

• V2AddlEnvironmentTests_SPEC2_18_Sessions_httpSession4
• V2AddlEnvironmentTests_SPEC2_18_Sessions_httpSession5
• V2AddlEnvironmentTests_SPEC2_18_Sessions_invalidate
• V2EnvironmentTests_PortletSession_ApiRender_getAttributeA4
• V2EnvironmentTests_PortletSession_ApiRender_getCreationTime2
• V2EnvironmentTests_PortletSession_ApiRender_invalidate1

Background:

According to PLT3 19.3,

If the HttpSession object is invalidated, the portlet container must also invalidate the corresponding PortletSession object. If a portlet invalidates the PortletSession object, the portlet container must invalidate the corresponding HttpSession object.

and PLT3 19.4.1

The PortletSession interface methods getCreationTime, getId, getLastAccessedTime, getMaxInactiveInterval, invalidate, isNew and setMaxInactiveInterval must provide the same functionality as the HttpSession interface methods with identical names.

The PortletSession interface getAttribute, setAttribute, removeAttribute and getAttributeNames methods must provide the same functionality as the methods of the HttpSession interface with identical names.

In Liferay, because of Equinox and the Whiteboard spec it follows, this can't be simply achieved by delegating to the underlying HTTP session.