You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Glenn Golden <gg...@umich.edu> on 2002/01/28 21:39:47 UTC
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?
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.
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.
Thanks!
- Glenn
--------------------------------------------
Glenn R. Golden, Systems Research Programmer
University of Michigan School of Information
ggolden@umich.edu 734-615-1419
http://www-personal.si.umich.edu/~ggolden/
--------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Portlet (jetspeed 1.3a2) architecture - actions
Posted by Santiago Gala <sg...@hisitech.com>.
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.
>
>
>Thanks!
>
>- Glenn
>
>--------------------------------------------
>Glenn R. Golden, Systems Research Programmer
>University of Michigan School of Information
>ggolden@umich.edu 734-615-1419
>http://www-personal.si.umich.edu/~ggolden/
>--------------------------------------------
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Portlet (jetspeed 1.3a2) architecture - actions
Posted by David Sean Taylor <da...@bluesunrise.com>.
> -----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 :
http://www.bluesunrise.com/jetspeed-docs/PortletAPIDraft.pdf
(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:
http://jakarta.apache.org/turbine/turbine-2/howto/action-event-howto.html
http://jakarta.apache.org/turbine/turbine-2/howto/velocity-site-howto.html
> 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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>