Folks,
The Portlet API 2 - that I am *still* working on - will have an action
concept. Implementation is up for grabs. Essentially, the idea is that the
portal server has to build up actions dynamically and register them for
particular URLs, that can then be inserted by the portlet at the appropriate
places. Of course, an action can consist of multiple actions.
When the URL is requested, either the portal server or the portlet will have
to handle the action(s). Actions are delivered to the portlet through
events. Also, I have defined a couple of window events that can be handled
by the portlet (if appropriate listeners are defined). At the moment I am
looking at cross-portlet communication through events.
The next iteration of the Portlet API should be ready within in a few
days -- stay tuned!
Cheers,
Thomas B.
----- Original Message -----
From: "Mirko Buholzer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 22, 2001 8:10
Subject: Re: Portlet Action ?
> Hi,
>
> Yes I mean, having a portlet that would support navigation in its
> "portletspace" i.e. window.
>
> I think then we should create a general approach for this (now). ;-)
>
> The approach of Manjuka is a way we can do it. But I think we should have
> an approach like the action components of the Turbine Page concept.
> We should be able to register a specific action for a specific Portlet.
> So only the getContent() method of this specific portlet is called.
>
> regards,
> Mirko
>
> --
> Sent through GMX FreeMail - http://www.gmx.net
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/[email protected]/>
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
