[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643395#action_12643395 ]
Felix Röthenbacher commented on PORTLETBRIDGE-48: ------------------------------------------------- Mike, Call to setRequestCharacterEncoding() originates in MyFaces API class javax.faces.application.ViewHandler: /** * Method must be called by the JSF impl at the beginning of Phase <i>Restore View</i> of the JSF * lifecycle. * * @since JSF 1.2 */ public void initView(javax.faces.context.FacesContext context) throws FacesException { String _encoding = this.calculateCharacterEncoding(context); if(_encoding != null) { try { context.getExternalContext().setRequestCharacterEncoding(_encoding); } catch(UnsupportedEncodingException uee) { throw new FacesException(uee); } } } Hth, Felix > 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.