[ http://issues.apache.org/jira/browse/MYFACES-1448?page=all ]
Scott O'Bryan reopened MYFACES-1448:
------------------------------------
MYFACES-434 apparently depends on a PortletRequest/Response object that is
derived off of HttpRequest/Response. This is not sufficient for Trinidad at it
is our goal to be container agnostic and work from WSRP containers as well.
Therefore we need a more generic and simpler solution. Trinidad needs the
MyFaces Bridge Portlet to provide code execution under to following conditions:
Portlet Initialization
Portlet Destruction
Pre-Lifecycle Request
Post-Lifecycle Request
And alternative to Pre-Lifecycle Request and Post-Lifecycle request might be:
Pre-Execute Request (takes PortletActionRequest/Response)
Post-ExecuteRequest
Pre-Render Request (takes PortletRenderRequest/Response)
Post-Render Request
> Enhanced initialization code execution
> --------------------------------------
>
> Key: MYFACES-1448
> URL: http://issues.apache.org/jira/browse/MYFACES-1448
> Project: MyFaces Core
> Issue Type: New Feature
> Components: Portlet_Support
> Environment: JSR-168
> Reporter: Scott O'Bryan
>
> The MyFaces Generic Portlet Bridge should be enhanced to allow special code
> to be executed during Portlet Initialization and Destruction, as well as
> before and after the lifecycle is run. Phase listeners do not always work
> for this because there is no guarantee that all phases will be executed for
> cleanup. This would allow a renderkit to provide SOME of the functionality
> which is commonly used in filters with the exception of Request/Response
> wrapping.
> Specification of these special "filters" would be defined in the portlet.xml
> and would be executed in the order that they are specified in that file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
