[PORTLETBRIDGE-43] MyFaces action handling sometimes fails with exception from ExternalContext setRequestCharacterSetEncoding

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0-beta, 2.0.0-alpha
• Fix Version/s: 1.0.0-beta, 2.0.0-alpha
• Component/s: Impl
• Assignee: Michael Freedman
• Reporter: Michael Freedman
• Created: 09/Jul/08 18:53
• Updated: 09/Dec/08 19:13
• Resolved: 09/Dec/08 19:13

Description

In some configurations (noteably when Facelets is used), an exception is thrown when MyFaces tries to set the request character encoding during an action. The exception claims that the request (parameters) have already been read and hence one can't do this set. This occurs because the Bridge reads the request parameters during ExternalContext construction to determine the view target of the request (if encodes this target in a render parameter). Fix is to delay determining the view until Faces actually tries to determine it itself. I.e. Don't resolve the view until either EC.getRequestPathInfo or EC.getRequestServletPath are called. Note: because at least older version of the Faces RI we support don't call these (in the portlet case) but rather relies on a request attribute being set – the bridge must also detect/resolve the view for this case as well.