I am trying to understand the event architecture in JSR286. Could you please provide some insight into how the pub/sub model works in case of JSR 286? My understanding is that public render parameters and eventing are the exactly the same architecture wise since they both follow a pub-sub model. Only difference being the complexity of payload and the callback mechanism that exists in the events. Having said that there must be an EventListener implemented by the portal vendor (not container) that will deliver or service the published events to their subscribers using the wiring admin tool. The EventListener will parse the portlet.xml file to get the information.
The JSR-286 provides capabilities for coordination between different portlets, that is, inter-portlet communication, with following mechanisms:
• sharing data between artifacts in same web application via session in application scope;
• using public render parameters in order to share render state between portlets;
• using portlet events that a portlet can receive and send
In this section we’re going to address the session, the public render parameters and the portlet events in detail.
Thanks for the reply. But the book is a paid one. I was just navigating through the TOC. BUt it seems that the books there only talk about how to achieve wiring in Lifery, but I really want to know the architecture of the pub-sub event model. Can you help me with getting the architectural details of ow the co-operation is getting achieved.
Jonas X. Yuan
Joined: May 18, 2008
The chapter 2 talks about generic JSR-286 - using Liferay portal as an example.