I've been looking at the JSR286 spec, and I'm still unsure if it was intended that public render parameters include the parameters from the page request. My reading says that they do not include the page parameters, but a few blogs on the net say they do.
I can use public render parameters to pass info between portlets, but have had no luck reading the page parameters with Jetspeed 2.2, even if I match the xml namespace to be identical to the page URL. Turning on the merge.portal.parameters.with.portlet.parameters option in jetspeed-portlet.xml works fine, but this is of course Jetspeed specific. Although we develop on Jetspeed, we deploy on IBM. Can anyone cast more light on this - it is a basic requirement for some applications. For instance, our customers have accounts of several types, and other applications (servlet, not portlet) would like to invoke our account information portlet, supplying the account type as a request parameter. Regards Ron --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
