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: Portlet (jetspeed 1.3a2) architecture - actions
Date Mon, 28 Jan 2002 21:38:33 GMT

> -----Original Message-----
> From: Glenn Golden [mailto:ggolden@umich.edu]
> Sent: Monday, January 28, 2002 12:40 PM
> To: Jetspeed-Dev (E-mail)
> Subject: Portlet (jetspeed 1.3a2) architecture - actions
> I'm new to Portlets, and I've been reading the Jetspeed and Turbine docs,
> and going through the code, and I'm confused about how a simple Portlet
> would be structured. What is the intended way it would place some
> buttons in
> its interface, and what is the intended way that these button presses come
> back to the Portlet code?

The Turbine way to do this is via actions.
We have VelocityPortlets, with Velocity actions.
See the HelloVelocity sample portlet.
Actions and events will be standardized in the Portlet API.
You can read the original Portlet API at :
(See chapter 7 on Portlet Events)
although this will merge with JSR-167 and will most likely change...

For now, I recommend using Turbine actions, and you can also leverage the
set of VelocityPortlets (CustomizerVelocity) work with Turbine actions
inside of a portlet.

For Turbine and actions see:

> I am just considering a simple ECS producing Portlet which extends
> AbstractPortlet (leaving the templates for later).
> Are we to use the action concept of Turbine for this? Is there
> some special
> naming convention that matches a form button to a method call in
> our portlet
> which is automatically called with the button press before
> getContent()? Or
> am I getting Turbine and Jetspeed confused?
> I see an example in the 1.3a2 distribution, the PollPortlet,
> which seems to
> just read form fields as parameters, just like, say, a servlet might do.
> This is pretty simple. Is this the intent for Portlets?
> The Portlet How To
> (http://www.bluesunrise.com/jetspeed-docs/PortletHowTo.htm) is
> good, but it
> doesn't have an example with a round trip button.

What do you mean by 'round trip'?
Im sorry but Ive been trying to finish the Tutorial for a while now, but as
usual docs keep getting 'prioritized'.
I will try to get a VelocityPortlet example in tonight.
Luc has already sent me all the code, I just need to write the docs and put
it on the website.
Any suggestions for the tutorial are welcome.

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

View raw message