Results 1 to 3 of 3

Thread: Skipping transactional joinpoint because no transaction manager has been configured

  1. #1
    Join Date
    Feb 2009
    Posts
    16

    Question Skipping transactional joinpoint because no transaction manager has been configured

    Hello,

    I use annotation-based declarative transaction management and compile-time weaving within an abstract @Service class.

    When running my code, I see log entries like this:
    Code:
    ...
    17:38:11.990 [main] DEBUG o.s.t.a.AnnotationTransactionAttributeSource - Adding transactional method 'findAll' with attribute: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
    17:38:11.990 [main] DEBUG o.s.t.a.AnnotationTransactionAspect - Skipping transactional joinpoint [ams.service.AbstractService.findAll] because no transaction manager has been configured
    17:38:12.006 [main] DEBUG o.s.o.j.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler - Creating new EntityManager for shared EntityManager invocation
    ...
    17:38:15.459 [main] DEBUG o.s.o.jpa.EntityManagerFactoryUtils - Closing JPA EntityManager
    ...
    In my initial context.xml, there is a transactionManager defined:
    Code:
    <context:spring-configured />
    
    <context:annotation-config />
    
    <tx:annotation-driven transaction-manager="transactionManager"
        mode="aspectj" />
    
    <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
      <property name="entityManagerFactory" ref="entityManagerFactory" />
    </bean>
    
    <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
      <property name="dataSource" ref="dataSource" />
      <property name="persistenceUnitName" value="AMS" />
      <property name="jpaVendorAdapter">
        <bean id="jpaAdapter" class="org.springframework.orm.jpa.vendor.EclipseLinkJpaVendorAdapter">
            <property name="database" value="H2" />
            <property name="generateDdl" value="true" />
            <property name="showSql" value="false" />
        </bean>
      </property>
    </bean>
    I use SpringFramework 3.0.5.RELEASE.


    Why do I get this message? How can I avoid it?

    Best regards,
    Lars

    PS: When compiling the sources, I see this warning. Does it matter?
    Code:
    [WARNING] advice defined in org.springframework.mock.staticmock.AnnotationDrivenStaticEntityMockingControl has not been applied [Xlint:adviceDidNotMatch]
    [WARNING] advice defined in org.springframework.mock.staticmock.AbstractMethodMockingControl has not been applied [Xlint:adviceDidNotMatch]
    [WARNING] advice defined in org.springframework.mock.staticmock.AbstractMethodMockingControl has not been applied [Xlint:adviceDidNotMatch]
    [WARNING] advice defined in org.springframework.scheduling.aspectj.AbstractAsyncExecutionAspect has not been applied [Xlint:adviceDidNotMatch]

  2. #2
    Join Date
    Dec 2010
    Posts
    315

    Default

    Did you annotate your service class with @Transactional?

  3. #3
    Join Date
    Feb 2009
    Posts
    16

    Default

    Hello skram,

    Quote Originally Posted by skram View Post
    Did you annotate your service class with @Transactional?
    Yes, the abstract class and multiple classes which extend the abstract class have the @Transactional annotation.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •