PortletRenderer prematurely closes response stream
--------------------------------------------------
Key: TAPESTRY-837
URL: http://issues.apache.org/jira/browse/TAPESTRY-837
Project: Tapestry
Type: Bug
Components: Portlet
Versions: 4.0
Environment: Windows XP
WebSphere Application Server 5.1
WebSphere Portal Server 5.1.
Reporter: Bart Bemindt
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.
-
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
