[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633787#action_12633787
]
Scott O'Bryan commented on PORTLETBRIDGE-48:
--------------------------------------------
Felix, we should maybe look at eliminating the cause of this exception rather
then just putting a bandaid on the symptom. The Portlet 1.0 Spec says the
following about throwing an IllegalStateException from setCharacterEncoding:
java.lang.IllegalStateException - if this method is called after reading
request parameters or reading input using getReader()
So IMO we should make sure that we set the content type before reading the
input stream and request parameters or, if we are, push back on Weblogic and
tell them they are doing things wrong. I find it likely that the bridge is
erroneously getting request parameters before setting the content type but I do
not have time to investigate right now.
If you'd like to do it and set another patch, then by all means. Otherwise
I'll assign it to another one of the comitters when I get a chance. My guess
is that the way things are architected between the GenericFacesPortlet and the
Bridge, this might not be a quick fix.
In either case, thanks for reporting it.
> 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.
