PortletExternalContextWrapper does not implement getRequestCharacterEncoding
for wrapped ExternalContext.
---------------------------------------------------------------------------------------------------------
Key: TOMAHAWK-1402
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1402
Project: MyFaces Tomahawk
Issue Type: Bug
Affects Versions: 1.1.8
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.
Reporter: FR Weichand
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
