[TAPESTRY-837] PortletRenderer prematurely closes response stream

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.0
• Fix Version/s: 4.2
• Component/s: Portlet
• Environment: Windows XP; WebSphere Application Server 5.1; WebSphere Portal Server 5.1.
• Assignee: Unassigned
• Reporter: Bart Bemindt
• Created: 13/Jan/06 23:55
• Updated: 18/Mar/07 18:54

Description

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.