portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18865] - [Enhancement] MVC Portlet Action Life Cycle
Date Fri, 11 Apr 2003 20:22:06 GMT
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=18865>.
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=18865

[Enhancement] MVC Portlet Action Life Cycle





------- Additional Comments From weaver@apache.org  2003-04-11 20:22 -------
>>Are you sure?
>>Thats the first thing I looked for when reviewing the MVC stuff, and it 
>>failed in my tests.
>>With the old VelocityPortlets, the portlet is available in the 
>>BuildNormalContext, but not in action events.
>>In my test, I tried to get the portlet in the action event, but no luck
>>Does this work for you (with JSP perhaps)?

> No, I'm not sure. I haven't tested it in Velocity but I'm pretty sure that it 
> worked for JSP under the old implementation. There's a method 
> PortletAction.getPortlet(Context context) which looks like would do it though.

The GenericMVCPortlet ALWAYS puts itself into the context prior to calling the 
action.

All of my portlets are VelocityPortlets I don't seem to be having any trouble 
retreiving the portlet via the PortletAction.getPortlet(Context).

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message