portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Kuebler <tkueb...@cisco.com>
Subject RE: [Bug 18865] - [Enhancement] MVC Portlet Action Life Cycle
Date Mon, 14 Apr 2003 19:25:45 GMT

Check out my event model proposal I sent last week, it covers actions 
outside of portlet context.

-tk

At 10:35 AM 4/14/2003 -0400, Weaver, Scott wrote:
> > Yes, I saw that. It did look hopeful at first, but its not right.
> > Turbine calls the action directly, it totally bypasses the Portlet MVC.
> > I debugged this straight from Turbine.java, no MVC code in the stack
> > trace of an action-event
>
>AFAIK, portlet actions should only be loaded/invoked from within the 
>portlets themselves and should not be a concern of the Turbine controller 
>servlet.  Am I wrong to think this?  I have always felt that if you need 
>to invoke an action outside the context of the portlet, you should use a 
>regular action event that is not an extension of VelocityPorletAction or 
>GenericMVCAction as they are reserved for use from within the portlet.
>
>*===================================*
>* Scott T Weaver                    *
>* Jakarta Jetspeed Portal Project   *
>* weaver@apache.org                 *
>*===================================*
>
>
>
> > -----Original Message-----
> > From: David Sean Taylor [mailto:david@bluesunrise.com]
> > Sent: Friday, April 11, 2003 4:32 PM
> > To: Jetspeed List
> > Subject: [Bug 18865] - [Enhancement] MVC Portlet Action Life Cycle
> >
> > >
> >
> > Sorry I can't be bothered with using Bugzilla. I still prefer threads
> > in the email list. :-)
> > see below
> >
> > > ------- 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.
> > >
> > Yes, I saw that. It did look hopeful at first, but its not right.
> > Turbine calls the action directly, it totally bypasses the Portlet MVC.
> > I debugged this straight from Turbine.java, no MVC code in the stack
> > trace of an action-event
> >
> > > All of my portlets are VelocityPortlets I don't seem to be having any
> > > trouble
> > > retreiving the portlet via the PortletAction.getPortlet(Context).
> > >
> > >
> > I tested this a few days ago.
> > Have you tested this within action events (not BuildNormalContext)?
> > Please reverify. That would be an awesome patch to Jetspeed.
> >
> >
> > --
> > 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


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