portlet to portlet communication

[Willem Vermeer]

Hello,

Does Hippo offer an out of the box solution for portlet to portlet communication? I want to pass some (form)-parameters from portlet A on page 1 to portlet B on page 2. What solutions are possible to support this scenario? I suppose I could submit a form on portlet A to portlet A but then how to pass control on to portlet B on page 2 sending the form parameters?

Thanks,
Willem

[David Sean Taylor-2]

On Aug 4, 2008, at 7:26 AM, Willem Vermeer wrote:

>
> Hello,
>
> Does Hippo offer an out of the box solution for portlet to portlet
> communication? I want to pass some (form)-parameters from portlet A  
> on page
> 1 to portlet B on page 2. What solutions are possible to support this
> scenario? I suppose I could submit a form on portlet A to portlet A  
> but then
> how to pass control on to portlet B on page 2 sending the form  
> parameters?
>
> Thanks,
> Willem

One solution, using "servlet" post parameters and making them  
available to all other portlets:

Turn on this setting in your override.properties (or  
jetspeed.properties):

#----------------------------------------------------------------------------------
# Until version 2.1, Jetspeed merged portal request parameters with  
portlet specific
# parameters, effectively allowing "shared" parameters.
# This is not compliant with the JSR-168 PLT.11, so by default this is  
now disabled.
#
# By setting merge.portal.parameters.with.portlet.parameters=true this  
feature can
# be "restored".
# In the situation of portal and portlet parameters with the same  
name, by default
# the portlet parameters will be provided first in the values array,  
but this too
# can be overridden by setting  
merge.portal.parameters.before.portlet.parameters=true
#
# Setting both these properties to true will deliver the "old" pre-2.1  
behavior.
# Note: for individual portlets, these global settings can be  
overridden by setting
#       these properties as metadata in jetspeed-portlet.xml
#----------------------------------------------------------------------------------
merge.portal.parameters.with.portlet.parameters=false
merge.portal.parameters.before.portlet.parameters=false

Another solution is to try the PortletMessaging classes available in  
Bridges
Note this solution just wrappers the webapp's session, and you cannot  
share session state across web apps

dtaylor@...  www.onehippo.com
San Francisco - Hippo USA Inc. 101 H Street, Suite Q Petaluma CA  
94952-3329 +1 (877) 41-HIPPO
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam [phone]

_______________________________________________
Hippoportal-dev mailing list
Hippoportal-dev@...
http://lists.hippo.nl/mailman/listinfo/hippoportal-dev