Nice, more Nabble. :-(
Ashish Parikh wrote:
Below is the process definition i was trying fork.. The node and
node1 are
running sequencially instead of parallel. I am putting wait in
MyActionHandler. It does not execute node1 till node is finished.
Realized that this is the default behavior for jbpm fork.. One way to run
the nodes in parallel is to add async=true property on node.. But it throws
JBPMServiceException: service 'message' unavailable. Any to configure
async=true would be appreciated.
We are using jbpm-jpdl 3.2.2 version.
<process-definition name='TestProcess'>
<start-state>
<transition name='fork' to='fork'>
</transition>
</start-state>
<fork name='fork'>
<transition to='node'></transition>
<transition to='node1'></transition>
</fork>
<node name='node'>
<action class='MyActionHandler' config-type='field'>
<inputs>inputs from node node;</inputs>
</action>
<transition to='join'></transition>
</node>
<node name='node1'>
<action class='MyActionHandler' config-type='field'>
<inputs>inputs from node1</inputs>
</action>
<transition to='join'></transition>
</node>
<join name='join'>
<transition to='node2' />
</join>
<node name='node2'>
<action class='MyActionHandler' config-type='field'>
<inputs>inputs from node2;</inputs>
</action>
<transition to='end'></transition>
</node>
<end-state name='end' />
</process-definition>