[WW-1224] Portlet URL support doesn't follow JSR-168 spec

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: WW 2.2.1
• Fix Version/s: WW 2.2.2
• Component/s: Plugin - Portlet
• Assignee: Nils-Helge Garli
• Reporter: Eric Dalquist
• Created: 02/Mar/06 20:18
• Updated: 17/Mar/06 09:20
• Resolved: 14/Mar/06 00:12

Description

The class com.opensymphony.webwork.components.URL uses the method HttpServletRequest.getQueryString() which is NOT available to portlets according to the JSR-168 specification.

This was discovered while trying to get the WebWork example portlet working in uPortal 2.5.X. uPortal adds parameters to the URL prefixed by uP_ which are treated as framework parameters and not passed on to the targeted portlet via the JSR-168 APIs.

In the URL class the WebWork framework is parsing the parameters off the URL which is retrieved by the HttpServletRequest.getQueryString() method. The results of this method cannot be considered valid for a portlet according to the JSR-168 specification. One possible fix would be to use the PortletActionContext.isPortletRequest() check and only perform URL inspection if not in a portlet.

Issue Links

• relates to: WW-1236 Missing test for null 'action' property in start() of URL component?