[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2606) Natural conversation id already in use in seam-bay example

[ http://jira.jboss.com/jira/browse/JBSEAM-2606?page=comments#action_12399044 ] Jacob Orshalick commented on JBSEAM-2606: ----------------------------------------- It appears the issue is that there is still a TODO to handle conversationName in org.jboss.seam.core.ConversationPropagation.restoreNaturalConversationId(Map) which seems to be the issue. I am adding a patch that handles retrieving the conversationId based on the parameter sent by the s:conversationName component. This works for my implemented example. The disadvantage to this is that the value for the <item-id> in the seam-bay example must be sent as an f:param. This would not be an issue if the s:conversationName tag not only sent the provided conversationName but based on the conversationName provided retrieved the conversation parameter-name and parameter-value from the context. This could then be sent along with the request in the same manner as the conversationName is currently allowing the conversation to be resumed. What do you guys think? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira