Dr. Carsten Leue, Architect, WebSphere Portal
Jaspreet Singh, Architect, Digital Experience
We will kick off the series with perhaps the most common yet useful concept of Public Render Parameters (PRP). We will focus on details of how state coordination via PRP works. In the handling of PRP there are many special cases and aspects. We will look at these various cases and understand how these can be best leveraged to develop your portal/portlet applications. One such case is the handling of resource parameters in comparison with public and private render parameters. Some examples are what happens if a resource parameter has the same name as a public render parameter, or how resource serving works with public and private render parameters etc.
Render Parameters concept
From the specification perspective, if you send query parameters to a render URL of a portlet, these query parameters become render parameters for that particular portlet. These are visible only to the portlet targeted by that render URL and not to any other portlet on the page. Also, if you append query parameters to portal URL instead, then these are not accessible to any portlet.
Thus, it is possible to write a form with method GET to set a render parameter. In our next blog, we will look into these details.