You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by bu...@apache.org on 2003/04/09 18:03:17 UTC
DO NOT REPLY [Bug 18867] New: -
[Enhancement] MVC Portlet Action Life Cycle
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18867>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18867
[Enhancement] MVC Portlet Action Life Cycle
Summary: [Enhancement] MVC Portlet Action Life Cycle
Product: Jetspeed
Version: 1.4b4-dev /CVS
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Enhancement
Priority: Other
Component: Portlets
AssignedTo: weaver@apache.org
ReportedBy: weaver@apache.org
CC: jetspeed-dev@jakarta.apache.org
Add a simple lifecycle to portlets, much in the same way that request-based pull
tools work.
I currently have implemented this within MVC portlets. The PortletAction class
now has a public init(Portlet, Context, RunData) method that is initialized
within the GenericMVCPortlet every time the portlet is loaded. The actual
initialization call is not done by the portlet but by a custom
PortletActionLoader class that wraps the existing ActionLoader and calls the
PortletAction init() method at load time.
PortletAction's init() currently populates protected fields such as "portlet",
"portletInstance", "runData" and "context" but could be overriden to provide
whatever initialization maybe required to action being invoked.
-scott
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org