topic Re: Differences About Parse Listeners b/w 5.11 and 5.12 in Alfresco Archive

Differences About Parse Listeners b/w 5.11 and 5.12

gokceng1 — Wed, 20 Mar 2013 14:35:23 GMT

Hi,I was using 5.11 till today and I was implementing my parse listeners that wayublic class ActivitiParseListener extends AbstractBpmnParseListener { private ExecutionListener executionListener; public ActivitiParseListener(ExecutionListener executionListener) { this.executionListener =

Re: Differences About Parse Listeners b/w 5.11 and 5.12

frederikherema1 — Thu, 21 Mar 2013 08:02:05 GMT

The listener-factory is intended to be used by activiti to create an Java-object to be used for ALL listeners. So this is not the best solution.

Have you read this piece in the user guide: http://activiti.org/userguide/index.html#advanced_parseHandlers ?

You can do something similar instead with user-tasks and add a task-listener instead.


public class CustomUserTaskBpmnParseHandler extends ServiceTaskParseHandler {
  
  protected void executeParse(BpmnParse bpmnParse, ServiceTask serviceTask) {
    
    // Do the regular stuff
    super.executeParse(bpmnParse, serviceTask);
    
    // Make always async
    ActivityImpl activity = findActivity(bpmnParse, serviceTask.getId());
    activity.setAsync(true);
  }

}

Re: Differences About Parse Listeners b/w 5.11 and 5.12

gokceng1 — Fri, 22 Mar 2013 09:34:08 GMT

Hi,
I've extended org.activiti.engine.impl.bpmn.parser.handler.CallActivityParseHandler and registered it like this:


 <bean id="myProcessEngineConfiguration" parent="someProcessEngineConfiguration">
  <property name="customDefaultBpmnParseHandlers">
   <list>
    <bean class="….demo.parse.CallActivityParseHandler">
     <constructor-arg name="executionListener" ref="activitiExecutionListener"/>
    </bean>
   </list>
  </property>
 </bean>

It works now, thank you.

Re: Differences About Parse Listeners b/w 5.11 and 5.12

frederikherema1 — Fri, 22 Mar 2013 15:33:24 GMT

Great, glad it helps. The Parse-handlers approach won't be changed anymore and is far more flexible than the earlier BPMNParseListeners.