Noel J. Bergman wrote: > > PLT 12.5.1 says, in part: > > 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 best can-do basis. > > This is a change from JSR-168 PLT 12.3.1. >
Please note also this draft 27 clarification, 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... I'd interpret that resource response falls outside matching process and getWriter is allowed without explicit setContentType call. -- Tuomas -- View this message in context: http://www.nabble.com/Content-Type-handling-for-JSR-286-tf4729371.html#a13525227 Sent from the Pluto - Dev mailing list archive at Nabble.com.
