request parameters are not preserved and persisted from the action to the
render request
----------------------------------------------------------------------------------------
Key: PORTLETBRIDGE-35
URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-35
Project: MyFaces Portlet Bridge
Issue Type: Bug
Components: Impl
Affects Versions: 1.0.0-alpha-2, 1.0.0-alpha, 1.0.0, 2.0.0
Environment: Myfaces 1.1.6 , WebLogic Portal 10.0 , Windows 2003
Server
Reporter: Angel Todorov
Priority: Critical
Fix For: 1.0.0, 2.0.0, 1.0.0-alpha-2, 1.0.0-alpha
When the Myfaces portlet bridge is used , and parameters are stored in the
initial request, they are not preserved, and the backend cannot reliably obtain
these parameters. This happens because normally in a portlet (JSR-168)
environment there are two requests - the action request, and the render
request. The problem is that the myfaces portlet bridge does not "transfer" all
of these request parameters from the action to the render request.
For example if I would like to use any AJAX framework that saves the ajax
components that need to be re-rendered, in the request, this won't work in a
portlet environment.
The solution is to get all request params in the action request, store them in
an object with a bigger scope than request scope, and then retrieve these
parameters in the render request, so that they are available to any entity on
the "backend" that can access the PortletContext / Servlet context.
What about storing these in the PortletSession object?
Thanks,
Angel
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
