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 Mon, 14 Apr 2003 19:51:30 GMT

On Monday, April 14, 2003, at 12:39  PM, Weaver, Scott wrote:

>> yes, but the params are still a mystery to me....
> I have updated the javadocs here and will commit them when we have a 
> resolution.  I'll have to remember to turn on the 
> "anal.javadocs.check=true", but I'm still having trouble finding that 
> one ;)

Hey stop complaining -- you started this ;-)

>> Well considering I have lots of actions written prior to
>> GenericMVCPortlet, would be safe to say that they will all fail...
>> This leaves at them at the exact state they were in before MVC 
>> portlet,
>> they can't access the portlet.
>> Could you quickly describe how I should port my actions so that they
>> work correctly in MVC?
> So these actions where broke prior to MVC and me gutting the Velocity 
> portlet/action implementation?  If not, I f***ed up big time on my 
> regression testing :(
No they weren't broken in that they worked as expected - no access to 
the portlet.
Again, Can you provide an example of converting a Turbine action event 
to MVC?
Still not sure how to code it into my template (JSP or Velocity)
There are examples of Turbine action events all over the Jetspeed 
source code.

> However, I was pretty confident that the MVC changes where backward 
> compatible since all of the customizer, admin and demo 
> portlets/actions seemed to be functioning correctly.
>> Don't get me wrong . I really welcome the MVC, It just doesn't seem
>> right to have the getContent() method is invoking actions.
>> Its good that the action phase completes for this particular portlet
>> before the render phase, but i would prefer that it completes before
>> all portlet's render phases.
> I think Todd did this because that's where the action phase was prior 
> to MVC.  I will look at moving action invocation up, outside the 
> portlet entirely.  Does that sound like a good approach?
No it wasn't. The Turbine action events kick off before render.

> p.s.
> Do we have and IRC channel?  We may be able to expedite this process 
> by using it as opposed to the list.  We could always log the IRC chat 
> and then post it to the bugzilla or to the home page or somewhere.

  werken.com 6667 #Jetspeed
I can be out there in 30 minutes or so
David Sean Taylor
Bluesunrise Software
+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

View raw message