Portlet 2.0 Bridge doesn't render correctly if event follows a render (without
any previous actions)
----------------------------------------------------------------------------------------------------
Key: PORTLETBRIDGE-134
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-134
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: Impl
Affects Versions: 2.0.0-alpha
Reporter: Michael Freedman
Assignee: Michael Freedman
Currently, the bridge doesn't establish a scope until the first action/event as
the scopeId is managed in a renderParam and one can't create such during a
render. Problem is that render is the operation that save's the view and
creates the VIEW_STATE param that the bridge caches in the request scope to
reuse when called in a redisplay. So if the first render is followed by doing
an operation in another portlet that causes an event to get sent to this
portlet, the event will establish a scope -- but there will be no VIEW_STATE
parameter -- As this isn't a client postback its not in the incoming request
and as we did establish a scope in the first render its not there. When the
render follows the event the render terminates prematurely (in some Mojarra
imples (in 1.2_05 and later) because it checks to see if we are in a psotback
(depends on this param) and when not sets responseComplete. Fix is to
establish the scope in the first render and temporarily cache it in the session
ala what is already done for resources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
