Spring and JPA vs Activiti and call activity

zze_one — Fri, 21 Mar 2014 14:08:30 GMT

Good morning Activiti,Guys I need your help (big time) concerning the integration of Activiti with Spring and JPA.The context.My bpmn files contain a text-annotation with a customized version number<textAnnotation id="versionNumber"> <text>1.10</text> </textAnnotation>‍‍‍‍‍

Re: Spring and JPA vs Activiti and call activity

trademak — Fri, 21 Mar 2014 15:54:02 GMT

Could you include the implementation of your CustomizedActivityBehaviorFactory class?

Thanks,

Re: Spring and JPA vs Activiti and call activity

zze_one — Fri, 21 Mar 2014 16:40:04 GMT

sure thing.
Thanks for having a look !

Re: Spring and JPA vs Activiti and call activity

zze_one — Wed, 26 Mar 2014 21:21:33 GMT

Hi again.

problem solved.
In CustomizedActivityBehaviorFactory, I Autowired my CustomizedCallActivityBehavior.

I also had to Inject the SpringProcessEngineConfiguration in the Rest Controller I was qwering.

In dispatcher-servlet.xml:
<import resource="classpath:activiti.cfg.xml" />

Re: Spring and JPA vs Activiti and call activity

jbarrez — Tue, 01 Apr 2014 19:12:36 GMT

It makes sense then it didn't work before 😉

Thanks for posting back the solution to your problem!

Re: Spring and JPA vs Activiti and call activity

zze_one — Wed, 23 Apr 2014 15:51:20 GMT

Hi Joram,

I'm attaching my CustomizedActivityBehaviorFactory class.

The purpose of this class is to create a CustomizedCallActivityBehavior bean instead of a CallActivityBehavior to manage call activities.
I'm overriding createCallActivityBehavior(CallActivity callActivity) for this purpose.

This solution works fine but I feel like it's not the best way of doing it.
If tomorrow you guys make changes in CallActivityBehavior, those changes won't be applied to my code. So maintainability is not optimized.

Is there a way to / do you have any suggestion for me to / provide a new CustomizedCallActivityBehavior without overriding the entire method ?

In <code>
@Override
public CallActivityBehavior createCallActivityBehavior(CallActivity callActivity) {
String expressionRegex = "\\$+\\{+.+\\}";

/**
   * In process-appContext.xml
   * CustomizedCallActivityBehavior's scope is described as 'prototype'
   * in order for each call Activity to have a newly created bean
   * */
callActivityBehaviour = (CustomizedCallActivityBehavior) appContext.getBean("customizedCallActivityBehavior");

     if (StringUtils.isNotEmpty(callActivity.getCalledElement()) && callActivity.getCalledElement().matches(expressionRegex)) {
      callActivityBehaviour.setProcessDefinitionExpression(expressionManager.createExpression(callActivity.getCalledElement()));
     } else {
      callActivityBehaviour.setProcessDefinitonKey(callActivity.getCalledElement());
     }

     for (IOParameter ioParameter : callActivity.getInParameters()) {
       if (StringUtils.isNotEmpty(ioParameter.getSourceExpression())) {
         Expression expression = expressionManager.createExpression(ioParameter.getSourceExpression().trim());
         callActivityBehaviour.addDataInputAssociation(new SimpleDataInputAssociation(expression, ioParameter.getTarget()));
       } else {
         callActivityBehaviour.addDataInputAssociation(new SimpleDataInputAssociation(ioParameter.getSource(), ioParameter.getTarget()));
       }
     }

     for (IOParameter ioParameter : callActivity.getOutParameters()) {
       if (StringUtils.isNotEmpty(ioParameter.getSourceExpression())) {
         Expression expression = expressionManager.createExpression(ioParameter.getSourceExpression().trim());
         callActivityBehaviour.addDataOutputAssociation(new MessageImplicitDataOutputAssociation(ioParameter.getTarget(), expression));
       } else {
         callActivityBehaviour.addDataOutputAssociation(new MessageImplicitDataOutputAssociation(ioParameter.getTarget(), ioParameter.getSource()));
       }
     }

     return callActivityBehaviour;
}
</code>
The only thing that changes is
<code>
       callActivityBehaviour = (CustomizedCallActivityBehavior) appContext.getBean("customizedCallActivityBehavior");

     if (StringUtils.isNotEmpty(callActivity.getCalledElement()) && callActivity.getCalledElement().matches(expressionRegex)) {
      callActivityBehaviour.setProcessDefinitionExpression(expressionManager.createExpression(callActivity.getCalledElement()));
     } else {
      callActivityBehaviour.setProcessDefinitonKey(callActivity.getCalledElement());
     }
</code>

Re: Spring and JPA vs Activiti and call activity

frederikherema1 — Thu, 24 Apr 2014 07:29:45 GMT

I don't see any way to make your code less tied to the implementation right now, other than changing activiti-code…

Re: Spring and JPA vs Activiti and call activity

zze_one — Tue, 29 Apr 2014 17:48:04 GMT

Thanks Frederik

topic Spring and JPA vs Activiti and call activity in Alfresco Archive

Spring and JPA vs Activiti and call activity

Re: Spring and JPA vs Activiti and call activity

Re: Spring and JPA vs Activiti and call activity

Re: Spring and JPA vs Activiti and call activity

Re: Spring and JPA vs Activiti and call activity

Re: Spring and JPA vs Activiti and call activity

Re: Spring and JPA vs Activiti and call activity

Re: Spring and JPA vs Activiti and call activity