You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pluto-dev@portals.apache.org by "David DeWolf (JIRA)" <pl...@jakarta.apache.org> on 2005/07/23 06:24:45 UTC

[jira] Resolved: (PLUTO-128) Pluto does not provide access to OutputStream

     [ http://issues.apache.org/jira/browse/PLUTO-128?page=all ]
     
David DeWolf resolved PLUTO-128:
--------------------------------

    Fix Version: 1.0.1-rc4
     Resolution: Fixed

Modified version of patch applied.

> Pluto does not provide access to OutputStream
> ---------------------------------------------
>
>          Key: PLUTO-128
>          URL: http://issues.apache.org/jira/browse/PLUTO-128
>      Project: Pluto
>         Type: Bug
>   Components: portlet container
>     Versions: 1.0.1-rc2
>     Reporter: Eric Dalquist
>     Assignee: David DeWolf
>      Fix For: 1.0.1-rc4
>  Attachments: patch1.txt
>
> The RenderResponse.getPortletOutputStream actually returns an OutputStream wrapper around a PrintWriter. This can cause character encoding problems. In PLT.12.3.2 it states that if a portlet uses the OutputStream it is responsible for any character encoding that needs to be done. This does not allow a portlet to output binary content in a portal that supports binary output from portlets.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira