[jboss-user] [JBoss Seam] - Re: Bug in explicit conversation id management in SEAM 1.2.1

[raffaele.camanzo]

anonymous wrote : 
  | You have defined this page to use a natural conversation id, and then you try to use other strategies *on the same page*?? 
  | 

Definitely no. Three Seam components, three pages, three navigation rules, to avoid any misunderstanding I created three separate projects too and made the tests again.
One project defines the conversation id in a natural way, another one defines it in the old fashion and the third one gets a generated conversation id.
The three projects have the same behaviour:
One link from the main page to the @Begin action of the conversation, from that link I move through the navigation rules in another page, the one related to that conversation. 

This is the target page:

  | <!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  | <ui:composition xmlns="http://www.w3.org/1999/xhtml"
  | 	    		xmlns:ui="http://java.sun.com/jsf/facelets"
  | 	  			xmlns:h="http://java.sun.com/jsf/html"
  | 	  			xmlns:f="http://java.sun.com/jsf/core"
  | 	  			xmlns:s="http://jboss.com/products/seam/taglib"
  | 	  			xmlns:c="http://java.sun.com/jstl/core"
  | 				template="template.xhtml">
  | 
  | <!-- context manager -->
  | <ui:define name="actioncontent">
  | 	<h:dataTable value="#{actionTwo.starttimes}" var="iter">
  | 		<h:column>
  | 			<h:outputText value="#{iter}" />
  | 		</h:column>
  | 	</h:dataTable>
  | 	
  | 	<h:form>
  | 		<s:link action="#{actionTwo.doIt}">
  | 			<h:outputText value="Press me I should run into #{conversation.id} conversation" />
  | 		</s:link>
  | 	</h:form>
  | </ui:define>
  | 
  | </ui:composition>
  | 

The s:link refers to an action of the Seam component actionTwo, such action simply adds a string to a list, I guess I'm in a LRC, the @Begin method of the actionTwo component returned the outcome of this page, the s:link propagate the conversation, then I expect that Seam holds the component (saved in the conversation context) in the current conversation, but this does not happen in the two test cases with explicit conversation id.
In the Seam-assigned conversation id test everything works properly.

I can post you both the test cases and a more detailed description, anyway, I don't think you need server logs of Seam.

Can you please answer to these two questions?

anonymous wrote : 
  | - Can I expect that if I click twice on a link connected to the start conversation of an explicit id conversation Seam will understand that I'm asking for that conversation and resumes it?
  | - Is it legal to use the Redirect API knowing the conversation id (regardless generated or explicit) in order to resume a conversation?
  | 
  | Both the questions without a LRC in place (s:conversationPropagation type="none")
  | 

Actually my application does not work with Seam 1.2.1, I'd like to move to a natural conversation id compliant usage and I want to avoid any misunderstanding of the framework.

Regards,
Raffaele Camanzo



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

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