portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject Re: [Bug 18865] - [Enhancement] MVC Portlet Action Life Cycle
Date Tue, 15 Apr 2003 14:24:08 GMT

On Tuesday, April 15, 2003, at 06:09  AM, Weaver, Scott wrote:

> 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.ForwardDemoActi 
> on")">
>
I often put the action as an Input parameter too. Or more recently, I  
am using portlet forwards to abstract the entire link.

> 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.
>
I think we've come full circle.
You're going to have to look into overriding the action loader, since  
the action is executed before any other Jetspeed code (its called from  
Turbine.java)
This leads to another issue:
Jetspeed and Turbine only execute one action (event) per request.
(the BuildNormal context is not really an action in my mind, but more  
of a pre-render phase, the whole thing is very bastardized...)
The portlet api also specifies only one action per request.
Is this also the way that the MVC portlet works?
Are you specifying an action event in the registry?
Many of my portlets have several action events available per action...

Anyway this is not really a new bug, since the portlet was never  
available in action events before or after the MVC framework was put in  
place.

--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646




---------------------------------------------------------------------
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