portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weaver, Scott" <Swea...@rippe.com>
Subject RE: [Bug 18865] - [Enhancement] MVC Portlet Action Life Cycle
Date Tue, 15 Apr 2003 13:09:12 GMT
Every thing works as it did in the past.  I have been working with David's actions and found
the issue concerning the absence of a portlet in the context.  David's form actions directly
call the action by passing the "action" as a parameter when the form is submitted causing
turbine to get a hold of it first and execute way before the portlet is even materialized.
  

Here is an example of how David invokes his actions:

<form action="$jslink.addPathInfo($jslink.ActionKey,"portlets.ForwardDemoAction")">

where as I have always used either $jslink.getPortletById or $jslink.Template which indirectly
sets the action by looking at the registry and directly invoking from the portlet as opposed
to through Turbine.

Nothing is has been broken by the MVC it's just that David had expected that, no matter how
the action was invoked, he would have access to the portlet.  IMOHO, this should be true and
we definitely need to review the action invocation and look at fleshing your lifecycle out
into it.


*===================================*
* Scott T Weaver                    *
* Jakarta Jetspeed Portal Project   *
* weaver@apache.org                 *
*===================================*
  


> -----Original Message-----
> From: Todd Kuebler [mailto:tkuebler@cisco.com]
> Sent: Tuesday, April 15, 2003 2:24 AM
> To: Jetspeed Developers List
> Subject: Re: [Bug 18865] - [Enhancement] MVC Portlet Action Life Cycle
> 
> 
> The event model I was refering to is not in the MVCPortlet and is in a
> post
> I sent out last week.  It is intended to add scoped event/action handling
> completely decoupled from turbine and at different points outside the
> portlet getContent method , but it is still in proposal form.  I have had
> no feed back to date on it.  I will be implementing it over the next
> couple
> of weeks and had planned to post my progress here.
> 
> For the MVCPortlet I just copied verbatim what was in the Velocity portlet
> regarding action handling except that the GMVCP Action class is provided
> that decouples the context,etc from velocity.  As far as I know the old
> velocity actions should also work.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message