Type: Technical Task
Affects Version/s: None
Fix Version/s: Master
This bug was discovered by the following tests in the Portlet 3.0 TCK:
Although these are tests that generally target Portlet 3.0 features, these tests happen to exercise Portlet 2.0 features like calling PortletSession.invalidate() followed by PortletRequest.getPortletSession(false). The problem is that the return value should be null but it is non-null.
1. Download and deploy the attached com.liferay.issue.lps77743.portlet.war artifact
2. Add com.liferay.issue.lps77743.portlet to a portal page
3. Reload the page
The com.liferay.issue.lps77743.portlet indicates "PortletSession is null"
The com.liferay.issue.lps77743.portlet indicates "PortletSession is NOT null"