[jboss-user] [JBoss Seam] - Re: Question about explicit conversation id

[bsmithjj]

I @In(jected) the conversation component into my bean and then added some code to dump the conversation id in the method invokation.  It looks like that's working correctly, it's the SeamTest.FacesRequest that appears to be losing track of the conversation id.

New AccessRequestManager2.startRequest() Code:

  |     @Begin(id="DraftAccessRequestID:#{draftAccessRequestMaster.id}",join=true)
  |     public void startRequest() {
  |         log.info("draftAccessRequestMaster.id = "+draftAccessRequestMaster.getId());
  |         log.info(conversation);
  |         log.info("conversation.id = "+conversation.getId());
  |         log.info("conversation.parentId = "+conversation.getParentId());
  |     }
  | 

with the following output during execution:


  | 14:12:28,093  INFO com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:59) - draftAccessRequestMaster.id = 6
  | 14:12:28,093  INFO com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:60) - org.jboss.seam.core.Conversation at 1fcb845
  | 14:12:28,093  INFO com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:61) - conversation.id = DraftAccessRequestID:6
  | 14:12:28,093  INFO com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:62) - conversation.parentId = null
  | 14:12:28,124  INFO com.evergreen.accesscontrol.AccessRequestManager2Test.(info:94) - conversationId = 1
  | 

So I see that the desired conversation id, DraftAccessRequestID:6, is being created the way I would like, however, the SeamTest.FacesRequest is not reflecting this.



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

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