nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

spring3.0.5 ActivitiException transactionManager is required

zhangmin

<bean id="dataSource" class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy">
    <property name="targetDataSource">
      <bean class="org.springframework.jdbc.datasource.SimpleDriverDataSource">
        <property name="driverClass" value="com.mysql.jdbc.Driver" />
        <property name="url" value="jdbc:mysql://localhost/test" />
        <property name="username" value="root" />
        <property name="password" value="" />
      </bean>
    </property>
</bean>

<bean id="txManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
    <property name="dataSource" ref="dataSource" />
</bean>

<bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
    <property name="databaseType" value="mysql" />
    <property name="dataSource" ref="dataSource" />
    <property name="transactionManager" ref="txManager" />
    <property name="databaseSchemaUpdate" value="true" />
    <property name="jobExecutorActivate" value="false" />
</bean>

<bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean">
    <property name="processEngineConfiguration" ref="processEngineConfiguration" />
</bean>
<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" />

Caused by: org.activiti.engine.ActivitiException: transactionManager is required property for SpringProcessEngineConfiguration, use org.activiti.engine.impl.cfg.StandaloneProcessEngineConfiguration otherwise

Find more posts tagged with

Comments

jbarrez

That looks ok.
That exception is thrown when no transactionManager is set, but that seems to be ok for you.

Could you give some more logging?

gergelydombi

Hi,

I experienced the same problem. The problem arose because I wanted to inject an autowired
member field (RepositoryService) to my spring managed JUnit test.
The root cause is that Activiti spring integration uses the default autowire strategy, while
I wanted to use a byType, annotation based injection to inject the repository service.

The solution:

I split the spring configuration into two pieces:

service-applicationContext.xml, that uses byType injection:

<br><?xml version="1.0" encoding="UTF-8"?><br><beans xmlns="<a href="http://www.springframework.org/schema/beans" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/beans</a>"<br> xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" rel="nofollow noopener noreferrer">http://www.w3.org/2001/XMLSchema-instance</a>" <br> xmlns:tx="<a href="http://www.springframework.org/schema/tx" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/tx</a>"<br> xsi:schemaLocation="<a href="http://www.springframework.org/schema/beans" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/beans</a> <a href="http://www.springframework.org/schema/beans/spring-beans.xsd" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/beans/spring-beans.xsd</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="http://www.springframework.org/schema/tx" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/tx</a> <a href="http://www.springframework.org/schema/tx/spring-tx-3.0.xsd" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/tx/spring-tx-3.0.xsd</a>"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; default-autowire="byType"><br><br><br> <bean id="repositoryService" factory-bean="processEngine"<br>&nbsp; factory-method="getRepositoryService" /><br> <bean id="runtimeService" factory-bean="processEngine"<br>&nbsp; factory-method="getRuntimeService" /><br> <bean id="taskService" factory-bean="processEngine"<br>&nbsp; factory-method="getTaskService" /><br> <bean id="historyService" factory-bean="processEngine"<br>&nbsp; factory-method="getHistoryService" /><br> <bean id="managementService" factory-bean="processEngine"<br>&nbsp; factory-method="getManagementService" /><br><br><br></beans><br>

and activiti.cfg.xml, that uses direct references:

<br><?xml version="1.0" encoding="UTF-8"?><br><beans xmlns="<a href="http://www.springframework.org/schema/beans" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/beans</a>"<br> xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" rel="nofollow noopener noreferrer">http://www.w3.org/2001/XMLSchema-instance</a>" <br> xmlns:tx="<a href="http://www.springframework.org/schema/tx" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/tx</a>"<br> xsi:schemaLocation="<a href="http://www.springframework.org/schema/beans" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/beans</a> <a href="http://www.springframework.org/schema/beans/spring-beans.xsd" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/beans/spring-beans.xsd</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="http://www.springframework.org/schema/tx" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/tx</a> <a href="http://www.springframework.org/schema/tx/spring-tx-3.0.xsd" rel="nofollow noopener noreferrer">http://www.springframework.org/schema/tx/spring-tx-3.0.xsd</a>"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; > <br> <bean id="dataSource"<br>&nbsp; class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy"><br>&nbsp; <property name="targetDataSource"><br>&nbsp;&nbsp; <bean class="org.springframework.jdbc.datasource.SimpleDriverDataSource"><br>&nbsp;&nbsp;&nbsp; <property name="driverClass"<br>&nbsp;&nbsp;&nbsp;&nbsp; value="com.microsoft.sqlserver.jdbc.SQLServerDriver" /><br>&nbsp;&nbsp;&nbsp; <property name="url" value="jdbc:sqlserver://localhost:1433" /><br>&nbsp;&nbsp;&nbsp; <property name="username" value="user" /><br>&nbsp;&nbsp;&nbsp; <property name="password" value="pass" /><br>&nbsp;&nbsp; </bean><br>&nbsp; </property><br> </bean><br><br> <bean id="transactionManager"<br>&nbsp; class="org.springframework.jdbc.datasource.DataSourceTransactionManager"><br>&nbsp; <property name="dataSource" ref="dataSource" /><br> </bean><br> <br> <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration"><br><br><br>&nbsp; <property name="databaseType" value="mssql" /><br>&nbsp; <property name="dataSource" ref="dataSource" /><br>&nbsp; <property name="transactionManager" ref="transactionManager" /><br>&nbsp; <property name="databaseSchemaUpdate" value="false" /><br>&nbsp; <property name="jobExecutorActivate" value="false" /><br>&nbsp; <property name="deploymentResources" value="classpath*:/diagrams/*.bpmn20.xml" />&nbsp;&nbsp; <br>&nbsp; <br><br> </bean> <br> <br><br> <bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean"><br>&nbsp; <property name="processEngineConfiguration" ref="processEngineConfiguration" /><br> </bean><br> <br> <tx:annotation-driven transaction-manager="transactionManager" />&nbsp; <br> <br></beans> <br>

This enables the SpringProcessEngineConfiguration to be injected as specified in the configuration.

In the JUnit test you can now reference the repository service via annotation:

<br><br>@Transactional<br>@RunWith(SpringJUnit4ClassRunner.class)<br>@ContextConfiguration(locations = {"classpath:service-applicationContext.xml", "classpath:activiti.cfg.xml"})<br>public class ProcessTestHelloworld {<br> <br> @Autowired<br> RepositoryService repositoryService;<br> <br> @Test<br> public void testSpring() {&nbsp; <br>&nbsp; String deploymentId = repositoryService<br>&nbsp;&nbsp;&nbsp; .createDeployment()<br>&nbsp;&nbsp;&nbsp; .addClasspathResource("diagrams/demo_bpmn.activiti.bpmn20.xml")<br>&nbsp;&nbsp;&nbsp; .deploy()<br>&nbsp;&nbsp;&nbsp; .getId();&nbsp; <br>&nbsp; System.out.println("*** Repository id: " + deploymentId);<br> }<br><br><br>

HTH,
Gergő

jbarrez

So if I understand you correctly, a rename of the beans should also do the trick (if I want to keep using the default auto-wiring)?

gergelydombi

My understanding is that if you use default autowiring then this problem should never occur.
Only when I switched to autowire byType I saw this problem. My suggested solution keeps the activiti
autowiring strategy as is, and enables the client to use another autowiring strategy (or keep the default).

So probably that is a good practice.

This is my first real interaction with activiti, all this info is based on previous spring experience
(and the fact that I tried and it worked

)

gergelydombi

I have to admit that so far I really like the job you guys have all done with activiti, the designer and the spring integration. It is a great tooling for a developer with a Spring background. It took only a business day to
set up everything (using MS SQL Server) and integrate to our Spring environment.

Well done!

jbarrez

Great to hear, ant thanks! Such posts really motivate us 🙂

giga_zhang

My understanding is that if you use default autowiring then this problem should never occur.
Only when I switched to autowire byType I saw this problem. My suggested solution keeps the activiti
autowiring strategy as is, and enables the client to use another autowiring strategy (or keep the default).

So probably that is a good practice.

This is my first real interaction with activiti, all this info is based on previous spring experience
(and the fact that I tried and it worked )

mustn't set the autowiring strategy.No matter what strategy you set, the exception will ben thrown