topic Re: spring3.0.5 ActivitiException transactionManager is required in Alfresco Archive

spring3.0.5 ActivitiException transactionManager is required

zhangmin — Fri, 25 Feb 2011 02:59:54 GMT

<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.Drive

Re: spring3.0.5 ActivitiException transactionManager is required

jbarrez — Fri, 25 Feb 2011 11:08:43 GMT

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?

Re: spring3.0.5 ActivitiException transactionManager is required

gergelydombi — Mon, 28 Feb 2011 20:38:55 GMT

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:


<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
 xmlns:tx="http://www.springframework.org/schema/tx"
 xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
                        http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd"
                        default-autowire="byType">


 <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" />


</beans>

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


<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
 xmlns:tx="http://www.springframework.org/schema/tx"
 xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
                        http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd"
                        > 
 <bean id="dataSource"
  class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy">
  <property name="targetDataSource">
   <bean class="org.springframework.jdbc.datasource.SimpleDriverDataSource">
    <property name="driverClass"
     value="com.microsoft.sqlserver.jdbc.SQLServerDriver" />
    <property name="url" value="jdbc:sqlserver://localhost:1433" />
    <property name="username" value="user" />
    <property name="password" value="pass" />
   </bean>
  </property>
 </bean>

 <bean id="transactionManager"
  class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
  <property name="dataSource" ref="dataSource" />
 </bean>
 
 <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">


  <property name="databaseType" value="mssql" />
  <property name="dataSource" ref="dataSource" />
  <property name="transactionManager" ref="transactionManager" />
  <property name="databaseSchemaUpdate" value="false" />
  <property name="jobExecutorActivate" value="false" />
  <property name="deploymentResources" value="classpath*:/diagrams/*.bpmn20.xml" />   
  

 </bean> 
 

 <bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean">
  <property name="processEngineConfiguration" ref="processEngineConfiguration" />
 </bean>
 
 <tx:annotation-driven transaction-manager="transactionManager" />  
 
</beans>

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:



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

HTH,
Gergő

Re: spring3.0.5 ActivitiException transactionManager is required

jbarrez — Tue, 01 Mar 2011 08:51:33 GMT

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)?

Re: spring3.0.5 ActivitiException transactionManager is required

gergelydombi — Tue, 01 Mar 2011 11:56:54 GMT

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 )

Re: spring3.0.5 ActivitiException transactionManager is required

gergelydombi — Tue, 01 Mar 2011 12:01:51 GMT

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!

Re: spring3.0.5 ActivitiException transactionManager is required

jbarrez — Tue, 01 Mar 2011 12:31:00 GMT

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

Re: spring3.0.5 ActivitiException transactionManager is required

giga_zhang — Wed, 30 May 2012 03:16:16 GMT

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