[jira] Commented: (PLUTO-438) Rev 26. resource response content type handling

["Tuomas Kiviaho (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PLUTO-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539462 ] 

Tuomas Kiviaho commented on PLUTO-438:
--------------------------------------

Forgot to mention in ResourceResponseImpl that spec states.

PLT.12.5.1 Content Type
For the RENDER RESPONSE the setContentType method must throw an
IllegalArgumentException if the content type set does not match (including wildcard
matching) any of the content types returned by the getResponseContentType method of
the PortletRequest object. For the RENDER RESPONSE the portlet container should
ignore any character encoding specified as part of the content type and treat the content
type as if the character encoding was not specified.

I removed render response content type existence check all together from resource response since it no longer isn't required.

PLT.11.1.8 Response Content Types
If the getResponseContentType or getResponseContentTypes methods are exposed
via an ResourceRequest the returned values should be based on the HTTP Accept header
provided by the client.

This isn't currently implemented, but wasn't actually in the perspective of this patch.

PLT.12.5.1 Content Type
If the portlet does not specify a content type before the getWriter or
getPortletOutputStream methods the portlet container assumes the content type of the
PortletRequest.getResponseContentType()method and resolves wildcards on a bestcan-
do basis.

I left out the writer and outputstream since I've not got a clear picture yet how to proceed with this one on resource response side.

> Rev 26. resource response content type handling 
> ------------------------------------------------
>
>                 Key: PLUTO-438
>                 URL: https://issues.apache.org/jira/browse/PLUTO-438
>             Project: Pluto
>          Issue Type: Sub-task
>            Reporter: Tuomas Kiviaho
>             Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>         Attachments: content-type.patch
>
>
> According to portlet-api javadocs the setContentType mime matching only applies to RenderResponse. 
> Following thread has more detailed description.
> <http://www.nabble.com/Content-Type-handling-for-JSR-286-tf4729371.html>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.