topic Activiti on Spring configuration issue with navigatorManager in Alfresco Archive

Activiti on Spring configuration issue with navigatorManager

macbarfuss — Tue, 26 Mar 2013 10:52:56 GMT

I try to get Activiti including Explorer (and Camel, doesn't matter here) running in a spring container.The Activiti Engine is working. (At least, there is no error on startup) But I can't get the explorer running.mvn camel:run dies with java.lang.reflect.InvocationTargetExceptionCaused by: org.spri

Re: Activiti on Spring configuration issue with navigatorManager

macbarfuss — Tue, 26 Mar 2013 13:33:12 GMT

Hi there!

I compared my configuration with the examlpe configuration attached to "Activiti In Action" (book-camel) and corrected some entries.

Now it runs.

Re: Activiti on Spring configuration issue with navigatorManager

frederikherema1 — Wed, 27 Mar 2013 12:03:47 GMT

Maybe you can share what you did wrong, can be interesting for other uses as well…

Re: Activiti on Spring configuration issue with navigatorManager

macbarfuss — Wed, 27 Mar 2013 12:46:56 GMT

Yes, you're right.

When I tried to get everything up I added the necessary beans and tried to start with mvn camel:run.

I first had errors here:


 <bean id="repositoryService" factory-bean="processEngine"
  factory-method="getRepositoryService" />
 <bean id="runtimeService" factory-bean="processEngine"
  factory-method="getRuntimeService" />
 <bean id="taskService" factory-bean="processEngine"
  factory-method="getTaskService" />
 <bean id="historyService" factory-bean="processEngine"
  factory-method="getHistoryService" />
 <bean id="managementService" factory-bean="processEngine"
  factory-method="getManagementService" />

I tried to figure out what was wrong and found similar bean configurations on the web with processEngingeConfiguration as factory-bean, like:


 <bean id="repositoryService" factory-bean="processEngingeConfiguration"
  factory-method="getRepositoryService" />
 <bean id="runtimeService" factory-bean="processEngingeConfiguration"
  factory-method="getRuntimeService" />
 <bean id="taskService" factory-bean="processEngingeConfiguration"
  factory-method="getTaskService" />
 <bean id="historyService" factory-bean="processEngingeConfiguration"
  factory-method="getHistoryService" />
 <bean id="managementService" factory-bean="processEngingeConfiguration"
  factory-method="getManagementService" />

Then this seamed to work until I got the error when I started this thread. I had to change things back as shown in the first code block.

But I'm sorry, I have no idea why this did not work and works now. Maybe I changed a dependency from maven but can't remeber.