You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2007/08/30 00:36:30 UTC
[jira] Resolved: (PLUTO-425) Implementation of GetLifecyclePhase
[ https://issues.apache.org/jira/browse/PLUTO-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus resolved PLUTO-425.
---------------------------------
Resolution: Fixed
Patches have been applied to both branches. Thanks Christian!
> Implementation of GetLifecyclePhase
> ------------------------------------
>
> Key: PLUTO-425
> URL: https://issues.apache.org/jira/browse/PLUTO-425
> Project: Pluto
> Issue Type: New Feature
> Components: portlet container
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Priority: Minor
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: lifecyclephase.290807.patch
>
>
> PLT.11.1.3.4 The Lifecycle Phase Request Attribute
> The LIFECYCLE_PHASE request attribute of the PortletRequest interface allows a portlet
> to determine the current lifecycle phase of this request. This attribute value must be
> ACTION_PHASE if the current request is of type ActionRequest, EVENT_PHASE if the
> current request is of type EventRequest, RENDER_PHASE if the current request is of type
> RenderRequest, and RESOURCE_SERVING_PHASE if the current request is of type
> ResourceRequest.
> The main intend of this method is allowing frameworks implemented on-top of the Java
> Portlet Specification performing the correct type casts from the
> PortletRequest/PortletResponse to a specific request/response pair, like
> ActionRequest/ActionResponse.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.