Use the same request as in the JSP from the ManagementToolbarDisplayContext classes

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: Adaptive Media, Announcements & Alerts widgets, Blogs > Analytics, Documents & Media, Item Selector, Knowledge Base widget, Message Boards, User Notifications
• Labels:
  • management-toolbar
  • must-for-7.1
• Priority Level: Low
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/58514

I have found that requests that come from `liferayPortletRequest.getHttpServletRequest()` do not behave the same as the original `request` available in the JSPs.

To avoid unexpected issues we should replace every use of `liferayPortletRequest.getHttpServletRequest()` inside ManagementToolbarDisplayContext classes with the request from the JSP via constructor.

The reason for this is that parameters added this way:

<liferay-util:include page=“/bookmarks/toolbar.jsp” servletContext=“<%= application %>“>
    <liferay-util:param name=“searchContainerId” value=“entries” />
</liferay-util:include>

En up creating a wrapped request that does not correspond to the one retrieved from the liferayPortletRequest.