portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Santiago Gala <sg...@hisitech.com>
Subject Re: Portlet (jetspeed 1.3a2) architecture - actions
Date Mon, 28 Jan 2002 22:37:42 GMT
Glenn Golden wrote:

>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?
>I am just considering a simple ECS producing Portlet which extends
>AbstractPortlet (leaving the templates for later).
ECS is mostly deprecated. Briefly: It does not scale well and it mixes 
Content and Logic.

Templates are actually simpler to program, and possibly to understand.

>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.
>Any pointers to docs I may have missed, or simple Portlet code that can be
>dropped in an email to this list to show how a simple button producing /
>responding portlet is supposed to work would be of great help to me and my
>team just now.
The model-view-controller paradigm is not completely there. Action 
buttons and generated URIs are the closest we have currently.

>- Glenn
>Glenn R. Golden, Systems Research Programmer
>University of Michigan School of Information
>ggolden@umich.edu           734-615-1419
>To unsubscribe, e-mail:   <mailto:jetspeed-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:jetspeed-dev-help@jakarta.apache.org>

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