-
1. Re: Explicit conversation id problem
gavin.king Mar 1, 2007 11:42 AM (in response to raffaele.camanzo)Please report it in JIRA, with a runnable test case.
-
2. Re: Explicit conversation id problem
lle Mar 1, 2007 1:16 PM (in response to raffaele.camanzo)Hi Raffaele ,
Can you please explain what is the mis-alignment and why it doesn't work and how did you fix it with the boolean value?
I am having some issue with explicit conversation Id and wondering if it is the same issue here.
Thanks
ly -
3. Re: Explicit conversation id problem
raffaele.camanzo Mar 2, 2007 9:03 AM (in response to raffaele.camanzo)Hi Gavin,
I added the issue and the test case, you can find them here:
http://jira.jboss.com/jira/browse/JBSEAM-976
I'm also trying to create a test case for the forum post:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102935
in order to understand if I can better explain what happens in my application, but, please can you have a glance at that, maybe I misunderstood something...
Thank you.
Hi Lle,
the problem is this one: in the documentation (6.6) there's a description of the Seam behaviour when multiple calls are made on the @Begin method of a conversation with a given ID; the behaviour expected is to avoid to call more than once the @Begin method, i.e. the first request which needs the creation of a conversation with a given ID causes the @Begin method call, further requests on that ID should skip the execution of such method; but this seems not to happen (at least to me).
the solution is straightforward: even if the @Begin method is called more than once Seam retrieves the correct conversation with it's status, then:private boolean passed = false; @Begin(join=true, id="<whateveryouneed>") public String startConversation() { if(! passed) { passed = true; // initialization here } }
Regards,
Raffaele Camanzo