[jboss-user] [JBoss Seam] - Re: conversationId and IPC Portlets

[frankr]

Both PortletA and B render a page that contain command links:


  | <h:commandLink action="#{controller.showContent}">
  | 		#{portal_messages['clickme']}
  | </h:commandLink>
  | 

Because of IPC all actions of PortletA and B are invoked on PortletB (the listening portlet). IPC is implemented using the standard example included in JBoss Portal.

The action method in the controller begins or joins the conversation:


  | @Begin(join = true)
  | public String showContent() {
  | 	...
  | 	return "show_content";
  | }
  | 

If I click the command link on PortletB, the behavior is as expected: the conversation starts and it stays in the same conversation on subsequent clicks, nothing wrong here.

When I click on the command link in PortletA, the content renders correctly in PortletB but with a new conversation ID which is again long running. After this also PortletB uses the new conversation ID. So this means every time I click a link in PortletA I get one extra long running conversation.

I either need a way to invoke the action in the controller from A without starting the new conversation or, as a work around, a way to cancel the new conversation and switch back to the old conversation again.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987773#3987773

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987773