• Portlet Guide
  • Quick tutorial: deploying the portlet test suite
  • Deployment
    • What is a portlet preparation? Why do I need it?
    • Deploying through the administration user interface
    • Deploying directly through the file system
  • Using in a Jahia page
    • Portlet instances
    • Portlet roles and Jahia permissions
  • Hello world portlet
    • Requirements
    • Project structure
    • Maven project descriptor
    • Portlet Java code
    • Portlet descriptor
    • Web application descriptor
    • The Tomcat deployment descriptor
    • Building and deploying
    • Redeployment
    • Troubleshooting deployment
    • Learning more
  • Support for Bridges
  • How to share portlet objects?
    • Public Render Parameters
    • Portlet Events
    • Jahia Shared Map
      • How to share a simple object?
      • How to read a simple object?
      • How to share a bean?
  • Performance
  • Using portlets on other application servers
  • Additional resources

Public Render Parameters

Public render parameters are intended for sharing view states across portlets. Using public render parameters instead of events avoids the additional event call process and enables the end-user using the browser navigation and bookmarking if the portal stores the render parameters in the URL.

An example of where public render parameters are useful is a weather portlet that wants to display the weather of a selected city. This portlet uses the public render parameters for encoding the zip code.

The user now adds additional portlets on the page that also have the zip code as one of their public render parameters, like a map portlet displaying the location of the city or a tourist information portlet displaying tourist information for the selected city.

For more details on public render parameters, see PLT.11.1.1.2.