Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

No bean named 'transactionManager' is defined

I have configured two persistent units with the entity managers set up as show below:

<bean id="liveEntityManagerFactory"            class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"           p:dataSource-ref="LiveDataSource">                      <property name="persistenceUnitName" value="LivePersistenceUnit" />     </bean>      <bean id="archiveEntityManagerFactory"            class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"           p:dataSource-ref="ArchiveDataSource">                      <property name="persistenceUnitName" value="ArchivePersistenceUnit" />     </bean> 

I then configured the transaction managers as

 <bean id="LiveTransactionManager"           class="org.springframework.orm.jpa.JpaTransactionManager"           p:entityManagerFactory-ref="liveEntityManagerFactory"/>      <bean id="ArchiveTransactionManager"           class="org.springframework.orm.jpa.JpaTransactionManager"           p:entityManagerFactory-ref="archiveEntityManagerFactory"/>   

I originally had just one configured and it was called "transactionManager". Addint an additional persistent unit seems to generate an error. One thing i dont understand, if i configured two persistent units (each for a separate database) do i also need to configure an individual entity manager and a transaction manager for each datasource?

The error that i get is shown below: (I have search all file and i cant find anywhere where there is a reference for "transactionManager")

org.springframework.ws.soap.client.SoapFaultClientException: No bean named 'transactionManager' is defined     at org.springframework.ws.soap.client.core.SoapFaultMessageResolver.resolveFault(SoapFaultMessageResolver.java:37)     at org.springframework.ws.client.core.WebServiceTemplate.handleFault(WebServiceTemplate.java:774)     at org.springframework.ws.client.core.WebServiceTemplate.doSendAndReceive(WebServiceTemplate.java:600)     at org.springframework.ws.client.core.WebServiceTemplate.sendAndReceive(WebServiceTemplate.java:537)     at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:384)     at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:378)     at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:370)     at com.ws.client.SoapTest.testFail(SoapTest.java:140)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:597)     at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)     at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)     at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)     at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)     at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)     at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)     at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)     at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)     at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)     at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)     at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)     at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)     at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)     at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)     at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)     at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)     at org.junit.runners.ParentRunner.run(ParentRunner.java:220)     at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)     at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)     at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)     at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:597)     at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)     at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)     at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)     at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)     at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) 

I am using Spring with Jpa/Hibernate.

Thanks

like image 851
ziggy Avatar asked May 23 '12 12:05

ziggy


People also ask

How do I fix Nosuchbeandefinitionexception?

The best solution is to properly isolate beans. The DispatcherServlet is responsible for routing and handling requests so all related beans should go into its context. The ContextLoaderListener , which loads the root context, should initialize any beans the rest of your application needs: services, repositories, etc.

What is spring boot transactional?

The @Transactional annotation is the metadata that specifies the semantics of the transactions on a method. We have two ways to rollback a transaction: declarative and programmatic. In the declarative approach, we annotate the methods with the @Transactional annotation.


2 Answers

The default value for the transaction-manager attribute is transaction-manager. In your case, you should specify which transaction manager you want to use per method or service like this:

@Service @Transactional(value="LiveTransactionManager")  class someClass... 

or

@Transactional(value="ArchiveTransactionManager")  public void someMethod 
like image 66
sebi Avatar answered Oct 07 '22 05:10

sebi


Actually, there is a way to use named TransactionManager with Spring Data JPA. This works for me:

<bean id="myTransactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">     <property name="entityManagerFactory" ref="myEntityManagerFactory" /> </bean> <tx:annotation-driven transaction-manager="myTransactionManager"/>  <jpa:repositories base-package="com.xxx.yyy" entity-manager-factory-ref="myEntityManagerFactory" transaction-manager-ref="myTransactionManager"> </jpa:repositories> 
like image 29
Jan Petersen Avatar answered Oct 07 '22 04:10

Jan Petersen