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 "Michael Blum (JIRA)" <pl...@jakarta.apache.org> on 2005/07/15 15:06:11 UTC

[jira] Resolved: (PLUTO-112) RenderResponseImpl.setBufferSize breaks servlet spec

     [ http://issues.apache.org/jira/browse/PLUTO-112?page=all ]
     
Michael Blum resolved PLUTO-112:
--------------------------------

    Fix Version: Current CVS
     Resolution: Fixed

I stalled the patches from Ulrich Kuester and tested them. All worked fine.

> RenderResponseImpl.setBufferSize breaks servlet spec
> ----------------------------------------------------
>
>          Key: PLUTO-112
>          URL: http://issues.apache.org/jira/browse/PLUTO-112
>      Project: Pluto
>         Type: Bug
>   Components: portlet container
>     Versions: 1.0.1-rc2
>     Reporter: Eric Dalquist
>      Fix For: Current CVS
>  Attachments: jira112_2_patch.txt, jira112_3_patch.txt, jira112_patch.txt
>
> The RenderResponseImpl.setBufferSize method always throws an exception. The servlet spec states that this method must be called before any response content is written or an exception will be thrown and that it cannot be called after content is starting to be written.
> When running in WebLogic the JSP parsing/rendering libraries used create code that calls the setBufferSize on the response. This results in an un-caught exception being thrown on WebLogic any time a JSP is rendered by a portlet.
> Commenting out the setBufferSize/getBufferSize methods of the RenderResponseImpl seem to fix the problem since the calls are just passed to the underlying HttpServletResponse.

-- 
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