Portlet to Portlet Across Pages

Question

Does anyone know the recommended way to do portlet to portlet interaction ACROSS
PAGES? i've seen the 'martini' portlet but this doesnt show how one portlet can
affect another portlet on a different page.
I've tried connecting webflows via proxy nodes (doesn't work right, causes portlet
B to be included in portlet A's page, which will cause errors)
I've started to do a "forward" customization to the portal like the "redirect"
example on dev2dev, but this doesn't work well either.
thansk

Answer 1

thanks, i appreciate the feedback. that's how i'm going to try it...
"William Young" wyoungATsapient.com wrote:
>
Heya Kurt,
We did almost the same thing you are trying to do (we had a quick search
input
box in our header instead of a portlet that appeared everywhere).
We implemented it using a tag such as this:
<portal:form event="bea.portal.framework.internal.refresh"
namespace="search"
pageName="SearchResultPage" name="frmBasicSearch" method="GET">
The SearchResultsPage rendered our SearchResultsPortlet. The search
results
portlet's webflow had the refresh event go directly the SearchIP (which
is a bit
weird...but it worked). We did this in Portal 4.0.
Will Young
"Kurt C" <[email protected]> wrote:
you could do this, but that doesn't require portlet to portlet communication
at
all. the point is that the search form should be painted on all screens
but display
it's results on only 1 page. The results "window" is very large, the
search form
is very small.
after some thought, i think the best way to do this is by doing an actual
page
change and passing the search criteria with the request. It's not ideal,
but i
think the only option for portlet to portlet across page boundaries
"Adnan Bukhari" <[email protected]> wrote:
I don't know much about your design but to keep things simple if you
design your
search portlet such that it also shows search result the you can use
the portlet
on both pages. Store search result in pipeline session.
Regards
Adnan
"Kurt C" <[email protected]> wrote:
The portlet can be made to post to itself. You can then have an
InputProcessor which can intercept the data and store it in the session.
Then when a user clicks on the second page, on refresh the second
portlet can retrieve the data from the session.but this doesn't accomplish the goal of sending the user from page1
to 2, they
are having to do it manually
Also, I think that instead of posting to the same page, the portletcan
be made to post to the second page after going through the input
processor. That way you can have the user fill in the form data,then
i've tried this with createPageChange url and with Proxy nodes (i.e.,
IP to IP
in another webflow , represented on another page)
and it doesn't work
i think maybe i can just do a regular "get" to the second page andlet
it do the
processing
Jalpesh Patadia <[email protected]> wrote:
Kurt C wrote:
Yes, i figured that. But what if portlet A (on page 1) is submittingform data
to portlet B (on page 2)? How does the form data get put into the
session?
I suppose
you can just do a pageChangeUrl tag and pass in the parameters,
but
then you really
couldnt' use any webflow , correct??The portlet can be made to post to itself. You can then have an
InputProcessor which can intercept the data and store it in the session.
Then when a user clicks on the second page, on refresh the second
portlet can retrieve the data from the session.
Also, I think that instead of posting to the same page, the portletcan
be made to post to the second page after going through the input
processor. That way you can have the user fill in the form data,then
hit submit which will then activate the second page. Once the portlet
in
the second page is being rendered, it can retrieve the informationfrom
the session and display appropriate information.
Thanks,
Jalpesh.
Jalpesh Patadia <[email protected]> wrote:
One way which I can think of is to put the data you want to share
into
the pipeline session. Then when the portlet on another page is
accessed,
it would fetch that data and then change it's display accordingly.
Thanks,
Jalpesh.
Kurt C wrote:
Does anyone know the recommended way to do portlet to portlet
interaction
ACROSS
PAGES? i've seen the 'martini' portlet but this doesnt show how
one
portlet can
affect another portlet on a different page.
I've tried connecting webflows via proxy nodes (doesn't work right,causes portlet
B to be included in portlet A's page, which will cause errors)
I've started to do a "forward" customization to the portal like
the
"redirect"
example on dev2dev, but this doesn't work well either.
thansk