topic Problem with Service task in Alfresco Archive

Problem with Service task

k_kunti — Fri, 07 Jan 2011 06:08:13 GMT

Hi AllI am facing an issue in the service task… while instantiating a new process from it.1. Initially I was creating runtime service in my java class implemented ActivityBehaviorpublic class DynamicProcessServiceTask implements ActivityBehavior{ public void execute(ActivityExecution arg0) throws

Re: Problem with Service task

mproch — Sat, 08 Jan 2011 23:57:06 GMT

Hi,
don't know if it helps, but when implementing ActivityBehaviour it's good to extend BpmnActivityBehaviour.
It has some helper methods, and then you basically do:


    public void execute(ActivityExecution execution) throws Exception {
         … <- here goes the real work
         performDefaultOutgoingBehavior(execution);
    }

The last line cause process to proceed.
Don't know if you can get activity object from JavaDelegate

Re: Problem with Service task

sruiz — Wed, 12 Jan 2011 22:03:20 GMT

I had the same problem. I think that within the execute method of the ActivitiBehaviour you should choose what sequence flow is going to take the service and signal it.

If you use JavaDelegate as interface it takes the after finishing execute method the next activity. Use it better.

To be confirmed by a developer.

Re: Problem with Service task

jbarrez — Thu, 13 Jan 2011 13:12:28 GMT

Correct. From the userguide:

To implement a class that can be called during process execution, this class needs to implement the org.activiti.engine.delegate.JavaDelegate interface and provide the required logic in the execute method. When process execution arrives at this particular step, it will execute this logic defined in that method and leave the activity in the default BPMN 2.0 way.

[EXPERIMENTAL] It is also possible to provide a class that implements the org.activiti.engine.impl.pvm.delegate.ActivityBehavior interface. Implementations have then access to the more powerful ActivityExecution that for example also allows to influence the control flow of the process. Note however that this is not a very good practice, and should be avoided as much as possible. So, it is advised to use the ActivityBehavior interface only for advanced use cases and if you know exactly what you're doing.