What are the disadvantages of using session to accomplish portlet communication?
On 9/23/06, Stefan Zoerner <[EMAIL PROTECTED]> wrote:
Hi Tim!
Unfortunately, the Portlet 1.0 specification does not include events or
messages between two portlets. Some vendors offer proprietary solutions
here.
If the portlets are within the same portlet application, you have the
option to share information between them via the portlet session. The
latter has two scopes, one of them (application scope) is per user and
portlet application.
It is possible to add/update something in the session with this scope
during the processAction of the first portlet, and read/react with the
second portlet within the render phase.
This proceeding has several disadvantages, but in your case, it may
work, and it is standard compliant ( i.e. your portlets will run and
interact on all specification conformant portal servers).
I hope this helps,
Stefan
