-
1. Re: Starting two tasks of different processes instances cause conversation error
pmuir Jul 16, 2008 11:55 PM (in response to mikool)There is a one to one correlation between conversations and tasks.
-
2. Re: Starting two tasks of different processes instances cause conversation error
mikool Jul 17, 2008 11:05 AM (in response to mikool)I understand but there must be a way to create somehow concurrent conversations. I mean If I start the first task it must be possible to start the second task as well.
I've tried to use@Begin(join=true)
as an additional annotation for my startTask method but still have the same problem. -
3. Re: Starting two tasks of different processes instances cause conversation error
mikool Jul 17, 2008 12:50 PM (in response to mikool)I've found out that it does not depend on how many process instances are running. Starting two different tasks (without ending them) even does not work in one process instance with mulit tasks in one node.
-
4. Re: Starting two tasks of different processes instances cause conversation error
pmuir Jul 17, 2008 2:39 PM (in response to mikool)Seam doesn't support multiple concurrent active conversations.
Try not propagating the current conversation and then starting the second task.
-
5. Re: Starting two tasks of different processes instances cause conversation error
mikool Jul 17, 2008 3:30 PM (in response to mikool)Hi!
Thanks for Reply.
1.) Concerning the concurrent active conversation: are you sure? I'm asking because there is this component:#{conversationList}
It maintains a list of concurrent conversations.
So, I don't really understand why seam should not support concurrent active conversations.2.) What do you mean by
not propagating the current conversation and then starting the second task
? -
6. Re: Starting two tasks of different processes instances cause conversation error
mikool Jul 18, 2008 2:14 PM (in response to mikool)I got a solution.
Before starting a task I use a@End
Annotation.
Example:@End @StartTask public String startTask(){ return "success"; }
Is this solution OK? I mean, maybe it will cause other problems in future? -
7. Re: Starting two tasks of different processes instances cause conversation error
pmuir Jul 18, 2008 3:22 PM (in response to mikool)
Mike Smithes wrote on Jul 17, 2008 15:30:
Hi!
Thanks for Reply.
1.) Concerning the concurrent active conversation: are you sure? I'm asking because there is this component:#{conversationList}
It maintains a list of concurrent conversations.Yes, it maintains a list of background conversations, not active ones.
So, I don't really understand why seam should not support concurrent active conversations.So what is your suggested implementation? I don't know how to support concurrent active conversations.
2.) What do you mean by
not propagating the current conversation and then starting the second task
?read the manual ;-)
-
8. Re: Starting two tasks of different processes instances cause conversation error
mikool Jul 18, 2008 3:50 PM (in response to mikool)Ok, I've read the manual again but couldn't find any information about concurrent active conversations.
What do you think about my solution for my problem:@End @StartTask public String startTask(){ return "success"; }
-
9. Re: Starting two tasks of different processes instances cause conversation error
toppac.toppac.gmail.com Jan 29, 2009 8:29 PM (in response to mikool)Out of curiosity why does the @StartTask have to begin a new conversation everytime? Why can it not join and existing conversation? I am facing a similar issue to Mike where there may or may not be a conversation already active when a user gets to a StartTask.