thanx for your reply.
I've tried it and doesn't seem to work in expected way.
My test case:
1) I designed simple process containing only ReceiverTask (and start, end events of course
)
2) I created main process containing start, end events and CallActivity task configured to call external process from point 1 and activiti:async parameter set to true.
3) I started main process from point 2
4) The complete process flow stopped in following situation: main process (point 2) shows CallActivity task as an active one and 'subprocess' (from point 1) shows ReceiverTask as an active one.
This state fits to the Activiti documentation I think. The asynchronous execution means that once process flow reaches any element with async=true, the client thread returns with 'response', but process flow (in activiti engine context) continues in synchronous execution. As far as I understood it, this 'async' parameter modifies way when client thread returns back to client of a WF engine, not the way how CallActivity task executes its subprocess. But maybe I misunderstood something.
I would need to reach following state in the situation described above. When subprocess from point 1 is called by 'async' CallActivity task from main process (point 2), the subprocess is started and waits for message in its ReceiverTask, but the main process continues immediately and correctly finishes. It means only 1 process instance has to be active.
thanx for any help or advice
I've tried it and doesn't seem to work in expected way.
My test case:
1) I designed simple process containing only ReceiverTask (and start, end events of course
)2) I created main process containing start, end events and CallActivity task configured to call external process from point 1 and activiti:async parameter set to true.
3) I started main process from point 2
4) The complete process flow stopped in following situation: main process (point 2) shows CallActivity task as an active one and 'subprocess' (from point 1) shows ReceiverTask as an active one.
This state fits to the Activiti documentation I think. The asynchronous execution means that once process flow reaches any element with async=true, the client thread returns with 'response', but process flow (in activiti engine context) continues in synchronous execution. As far as I understood it, this 'async' parameter modifies way when client thread returns back to client of a WF engine, not the way how CallActivity task executes its subprocess. But maybe I misunderstood something.
I would need to reach following state in the situation described above. When subprocess from point 1 is called by 'async' CallActivity task from main process (point 2), the subprocess is started and waits for message in its ReceiverTask, but the main process continues immediately and correctly finishes. It means only 1 process instance has to be active.
thanx for any help or advice
one more question.
when this kind of behavior/feature is not supported by activiti engine out of the box, can not I face any other problems or side effects? I mean, when this 'asynchronous' execution of subprocesses is not supported by CallActivity task directly and I will implement it as a custom ServiceTask, can not it be something against some activiti general ideas and concepts?
just to be sure I will not face any other related, conceptual problem in near future
thanx a lot anyway
when this kind of behavior/feature is not supported by activiti engine out of the box, can not I face any other problems or side effects? I mean, when this 'asynchronous' execution of subprocesses is not supported by CallActivity task directly and I will implement it as a custom ServiceTask, can not it be something against some activiti general ideas and concepts?
just to be sure I will not face any other related, conceptual problem in near future
thanx a lot anyway
