trinidad requeststatemap does not preserve its state between action and render
------------------------------------------------------------------------------
Key: TRINIDAD-1863
URL: https://issues.apache.org/jira/browse/TRINIDAD-1863
Project: MyFaces Trinidad
Issue Type: Bug
Components: Portlet
Environment: JSF 2.0, Portlet
Reporter: Scott O'Bryan
Assignee: Scott O'Bryan
The Trinidad configurator framework stores some persisted state in an object
called the RequestStateMap. The RequestStateMap's lifespan is supposed to be
on physical request which, in a portlet environment, means one
processAction/render pair in the case of an ActionRequest, one
processEvent/render pain in the case of an event request, or the entire render
or resource requests. This is done by checking for the type of request and, if
the request is an eventRequest or actionRequest, the map is saved off to the
session before the actionRequest ends and then is retrieved from the session
when the next renderRequest is executed. Currently, however, this state is
getting saved to the RequestMap rather then the session where it belongs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
