I worked a bit on the event controller context which is an interface for performing event coordination in the new portlet controller module. Here are the principles of event control: 1/ when a portlet window produces an event this event is given to the event controller context that can react to that event and queue new events for consumption. 2/ when an event is queued for consumption, it will be delivered to the target portlet window. In each cases the event could be ignored by the controller, for instance if the portlet window produces an event that it does not publish in its metadata or if the event controller context creates an event that cannot be consumed by the target window id. So here I am talking about "portlet window" and not portlet. A portlet window has a window id and reference a portlet. This notion of window of course only pertains to the environment but actually we don't care much here. Here is an exemple with portlet windows A,B and C. 1/ user click on portlet A which is a process action 2/ A is invoked and fires event foo : it is a produced event [A,foo] 3/ the event controller is invoked and in reaction queues event [B,bar] and [C,bar] 4/ [B,bar] is consumed by B and produces [B,juu] 5/ [C,bar] is consumed by C and produces [C,daa] 6/ the event controller is invoked with [B,juu] but chose to do nothing (so the event is 'discarded') 7/ the event controller is invoked with [C,daa] and in reaction queues the event [A, zii] 8/ [A,zii] is delivered and consumed by A that does not produce anything in reaction 9/ we are done!!! I hope it is clear So for the JBPC I want to have an event debugger that would be used with a JSP tag that would display in the page a list of the events that would help developers to understand what happened during the action/event phase and my need is that someone comes up with the best system to display that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133023#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...