RE: Inter-Portlet communication, WebSphere Portal and JSR168

>I had the impression that calls to portlet methods were triggered 
>by browser requests, as opposed to being triggered 
>by say an entry on a data queue, or a   JavaSpace. 

The initial request is triggered by a browser request. The inter-portlet
communication comes into play when one (or more) portlets are interested
in something that happens in other portlets.

Imagine a portal w/3 portlets. One portlet is a list of customers, with
the customer # as a clickable link. The second portlet lists the
demographics (name, addr, etc.) for a customer, and the thrid shows the
open orders for a customer. If I click on customer 1 in portlet 1, I'd
like portlets 2 and 3 to reflect the demo and orders for customer 1, if
I click on customer 2 I want them to show the info for customer 2, etc. 

In order to do that I need a way for a change in portlet 1 to be
communicated to portlets 2 & 3, and that's IPC.

-Walden

------------
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)