-
1. Re: Programatically setting the taskInstance of the current
gavin.king Jun 15, 2006 2:47 AM (in response to slienert)Process.instance().setProcessId(pid)
Should work. -
2. Re: Programatically setting the taskInstance of the current
gavin.king Jun 15, 2006 2:47 AM (in response to slienert)Oh and then Process.instance().setTaskId()
-
3. Re: Programatically setting the taskInstance of the current
slienert Jun 15, 2006 3:05 AM (in response to slienert)Thanks Gavin, I'll give that a try
btw, is it really 3 in the morning over there ? You guys really take your 24 / 7 support seriously ;-) -
4. Re: Programatically setting the taskInstance of the current
gavin.king Jun 15, 2006 3:19 AM (in response to slienert)heh, no actually it is just 12, we are in Las Vegas for JBoss World :-)
-
5. Re: Programatically setting the taskInstance of the current
slienert Jun 19, 2006 2:37 AM (in response to slienert)Hi Gavin,
That worked. The business process context now picks up the correct process / task.
(I got rid of the @BeginTask annotation on the method)
My app sets the task and then navigates to a new page to work on this task, however the business process context seems to get reset by the next event, so that when I submit the new form the business process context has gone. Can I stop that from happening ?
I am using Seam 1.0 beta1.
Thanks,
Simon -
6. Re: Programatically setting the taskInstance of the current
gavin.king Jun 19, 2006 6:37 AM (in response to slienert)Easily fixed: just start a conversation.
-
7. Re: Programatically setting the taskInstance of the current
slienert Jun 19, 2006 9:43 PM (in response to slienert)Thanks Gavin,
That worked as well.
Now I just have to go away and work out the relationship between a conversation context and the business process context so I know why it worked !
Cheers,
Simon