[
https://issues.apache.org/jira/browse/TOMAHAWK-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated TOMAHAWK-1402:
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.9-SNAPSHOT
Assignee: Leonardo Uribe
Status: Resolved (was: Patch Available)
Thanks for provide this patch
> 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
> Assignee: Leonardo Uribe
> Fix For: 1.1.9-SNAPSHOT
>
> Attachments: PortletExternalContextWrapper.java
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
