AnsweredAssumed Answered

ProcessEngines.getDefaultProcessEngine() strange behavior

Question asked by houstoniasian on Oct 24, 2013
Latest reply on Oct 25, 2013 by trademak
I have two Java Apps using Maven to download Activiti 5.14 JAR.  Both have this line of code:

processEngine = ProcessEngines.getDefaultProcessEngine();

The first app, I have 5.14 JAR.  I set classpath in Eclipse to look for activiti.cfg.xml file.  This app works fine.

The 2nd app, I also have 5.14 JAR.  I set classpath in Eclipse to look for activiti.cfg.xml file.  For some reasons, Eclipse never looks for the config file.  As a result, my processEngine is null.  At first, I thought there is something wrong with the way I set my classpath.  However, when I change 5.14 to 5.11 in the pom.xml file in the 2nd app, it works.  This means, ProcessEngines.getDefaultProcessEngine() in the 2nd App would look for activiti.cfg.xml file when I use 5.11 JAR but it's not when 5.14 JAR is used.

I don't know how to explain this as I have Activiti 5.14 JAR in my first app and it works fine.

Can anyone think of why this happens?

Tan

Outcomes