How to receive the custom event in the listening portlet (No backing file)

Question

I have couple of portlets (JPF based). Portlet A is firing an event
     public Forward processAction()
          PortletBackingContext context =PortletBackingContext.getPortletBackingContext(this.getRequest());
          String message = "XXXXX";
          context.fireCustomEvent("customevent", message);
          Forward forward = new Forward("success");
          return forward;
I have configured the Portlet B's eventhandler to listen for the 'customEvent' and invoke the pageFlowAction 'listenForEvent'
     @Jpf.Action(forwards = { @Jpf.Forward(name = "success", path = "test2.jsp") })
     public Forward listenForEvent() {
          Forward forward = new Forward("success");
          return forward;
Portlet B's method listenForEvent is indeed getting invoked, but is there a way I can retrieve the 'Event' object (as fired by Portlet A) inside the listenForEvent. I could have done this via the Backing file, but for some reasons i cann't use the backing file. Is there a way i can get the CustomEvent and the associated payload in my listening JPF portlet, without a backing file?
The WLP version is 10.3

Answer 1

Hello,
I originally said:
All you should need to do is to modify the method signature for your event-receiving method. The method signature should be:
public void listenforEvent(HttpServletRequest request, HttpServletResponse response, Event event)
where Event is a com.bea.netuix.events.Event object. You can then cast this to a CustomEvent object.
But I mis-read your earlier post about catching the custom event and invoking a pageflow action. When you do that, you will lose the custom event's payload (your message), and there is no way to retrieve it from your pageflow action.
The only way you can actually retrieve the event's payload is using a backing file for the portlet, with a method having the signature I mentioned above. You can then set a request attribute with the event's payload and still have it invoke the pageflow action, at which time you could retrieve the request attribute value-- assuming you don't need to run this portlet over WSRP. Over WSRP, the event-handling and pageflow action-invoking lifecycles will happen with independent request objects, so you would need to store the event payload in session to work over WSRP.
Kevin
Edited by: kfrender on Aug 31, 2009 3:34 PM