[jira] Updated: (TAPESTRY-837) PortletRenderer prematurely closes response stream

["Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesse Kuhnert updated TAPESTRY-837:
-----------------------------------

    Fix Version/s:     (was: 4.1.2)
                   4.2

> PortletRenderer prematurely closes response stream
> --------------------------------------------------
>
>                 Key: TAPESTRY-837
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-837
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Portlet
>    Affects Versions: 4.0
>         Environment: Windows XP
> WebSphere Application Server 5.1
> WebSphere Portal Server 5.1.
>            Reporter: Bart Bemindt
>             Fix For: 4.2
>
>
> While toying around with Tapestry 4 portlet support in WebSphere portal server, I noticed that I could only ever have one Tapestry portlet shown on a portal page. Apparently the response was cut of after this one portlet was rendered. (Not even a closing </html> tag.)
> After some investigating I noticed that the problem was solved if I commented out the "writer.close();" line in the PortletRendererImpl class. Though I'm not sure if this has any side-effects.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org