[TOMAHAWK-1402] PortletExternalContextWrapper does not implement getRequestCharacterEncoding for wrapped ExternalContext.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.8
• Fix Version/s: 1.1.9
• Component/s: Portlet_Support
• Environment: Tomahawk on JSF RI within the JBOSS Portlet Bridge, the portlet bridge fails to resolve the Encoding and throws an UnsupportedOperationException. Resolving fails in the PortletExternalContextWrapper, which lacks a getRequestCharacterEncoding.
• Assignee: Leonardo Uribe
• Reporter: FR Weichand
• Created: 13/Mar/09 08:57
• Updated: 16/Jun/09 01:35
• Resolved: 26/May/09 23:17

Description

PortletExternalContextWrapper implements
setResponseCharacterEncoding
getResponseCharacterEncoding,
setRequestCharacterEncoding,
but not a getRequestCharacterEncoding.
When the wrapper is used as the external faces context in a portlet bridge (e.g. JBOSS portlet bridge), the resolving of the RequestCharacterEncoding defaults to the inherited method from ExternalContext (which returns an invalid encoding).

Implementing getRequestCharacterEncoding analogue to getResponseCharacterEncoding resolved the issue for me, the PortletExternalContextWrapper now works in a portlet environment.

The Bug prevents usage of Tomahawk within the JBOSS portlet bridge.