• 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

Portlet Events

Portlet events are intended to allow portlets to react to actions or state changes not directly related to an interaction of the user with the portlet. Events could be the result of a user interaction with other portlets. The portlet event model is a loosely coupled, brokered model that allows for creating stand-alone portlets that can be wired together with other portlets at runtime

An example of where a portlet may want to offer receiving events is for stating changes triggered by simple user interactions, e.g. adding an item to a shopping cart. Offering this as an event to other portlets can trigger adding items to the shopping cart based on the user’s interactions within these portlets. Unlike using the portlet application scope session, this will work across portlet application boundaries.

For more details on events, see PLT.15.