[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633987#action_12633987 ]
Felix Röthenbacher commented on PORTLETBRIDGE-48: ------------------------------------------------- Hi Scott, I did a quick test calling setCharacterEncoding() first of all in the GenericFacesPortlet's processAction() method and got the IllegalStateException. For me it looks like that either Websphere Portal has accessed the stream/request parameters before or that something is wrong with their com.ibm.ws.portletcontainer.core.impl.PortletRequestImpl implementation. The patch I provided makes the portlet bridge working in IBM WebSphere Portal 6.1 together with MyFaces Trinidad (see also http://issues.apache.org/jira/browse/TRINIDAD-1239) and this is what our primary objective was. But it's probably a good idea to file a bug report with IBM if this emerges to be their bug. > IllegalStateException in Websphere Portal. > ------------------------------------------ > > Key: PORTLETBRIDGE-48 > URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-48 > Project: MyFaces Portlet Bridge > Issue Type: Bug > Components: Impl > Affects Versions: 1.0.0 > Environment: IBM Websphere Portal 6.1 > Reporter: Felix Röthenbacher > Attachments: PortletExternalContextImpl.java.diff > > > The bridge tries to set the character encoding in the action phase. In > Websphere Portal this results in an IllegalStateException as the HTTP body > seems to be accessed already by the portal server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.