I think you have to wire the transactionmanager into the JmsConfiguration.

See:
http://cxf.apache.org/docs/using-the-jmsconfigfeature.html

Christian


Am 27.05.2011 12:17, schrieb mymacin:
Here is my spring bean configuration



        <context:component-scan base-package="foo"/>
        <context:annotation-config />

        
        <aop:config />


                <bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
                <property name="jpaVendorAdapter">
                <bean 
class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"
p:database="MYSQL" p:showSql="false"/>
                </property>
                
                
        </bean>

        <bean id="JTAtransactionManager"
class="org.springframework.transaction.jta.JtaTransactionManager">
         <property name="transactionManagerName"
value="java:/TransactionManager"/>
         <property name="userTransactionName" value="UserTransaction"/>

     </bean>

        <context:annotation-config/>

<tx:annotation-driven transaction-manager="JTAtransactionManager"/>

        <bean
class="org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor"/>



  <bean id="jmsConnectionFactory"
class="org.springframework.jms.connection.SingleConnectionFactory">
        <property name="targetConnectionFactory">
                <bean class="org.apache.activemq.ActiveMQConnectionFactory">
                        <property name="brokerURL" value="tcp://localhost:61616" 
/>
                </bean>
        </property>
</bean>


--
View this message in context: 
http://cxf.547215.n5.nabble.com/SOAP-over-JMS-Transactions-tp4431341p4431433.html
Sent from the cxf-user mailing list archive at Nabble.com.


Reply via email to