[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-141.
--------------------------------------------
Fix Version/s: 1.0.0
Resolution: Fixed
Problem was header names list wasn't being held in a case-insensitive manner --
i.e. they should be stored all caps but weren't.
> External context implementation returns content-type header
> -----------------------------------------------------------
>
> Key: PORTLETBRIDGE-141
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-141
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 2.0.0-alpha
> Environment: TCK running in WLS environment with Oracle portlet
> container
> Reporter: Alistair Wilson
> Assignee: Michael Freedman
> Priority: Minor
> Fix For: 1.0.0, 2.0.0
>
>
> The TCK test, getRequestHeaderMapRender, is failing when the CONTENT-TYPE
> header is returned in ExternalContext#getRequestHeaderMap.
> According to section 6.1.3.1 of the portlet bridge spec,
> "This Map must include the set of properties available via the
> javax.portlet.PortletRequest methods getProperty() and getPropertyNames()
> except when executing a RENDER_REQUEST. Within a RENDER_REQUEST, the map
> must exclude the CONTENT-TYPE property (if it is present in the underlying
> request). "
> The org.apache.myfaces.portlet.faces.util.map.PortletRequestHeaders class
> should check for and exclude the CONTENT-TYPE header when returning headers
> from the contained PortletRequest object. The TCK test for
> getRequestHeaderValuesMap is also failing. Fixing PortletRequestHeaders
> should solve this problem as well.
> The issue is not seen in the Pluto portlet container.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
