Complete Task Invocation Won't Return Immediately?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2011 05:11 AM
I've read the source code roughly
and I found that Activiti uses the very thread of client's service call rather than creating a new thread to continue the process, therefore, a complete task service call will be halted until the execution runs into another non-automatic activity (a user task for example) or until the whole process ends. This might not be acceptable when there were a lot of automatic and time-consuming tasks (such as web service calls) behind.
Maybe I've come to a wrong conclusion.
Thanks!
and I found that Activiti uses the very thread of client's service call rather than creating a new thread to continue the process, therefore, a complete task service call will be halted until the execution runs into another non-automatic activity (a user task for example) or until the whole process ends. This might not be acceptable when there were a lot of automatic and time-consuming tasks (such as web service calls) behind.
Maybe I've come to a wrong conclusion.
Thanks!
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2011 11:51 AM
No, correct conclusion. This will be 'fixed' if http://jira.codehaus.org/browse/ACT-126 is implemented. Then you can make the first task after the one you complete to return 'control'
