Dear majaa majaa, thank you for your reply!
Since the AppFuse 1.9.4. is adopting Spring 2.0, I think the code was transformed to the new declarations. The spring reference documentation 2.0, Chapter 9 states: Declarative transaction configuration in versions of Spring 2.0 and above differs considerably from previous versions of Spring. The main difference is that there is no longer any need to configure TransactionProxyFactoryBean beans. The old, pre-Spring 2.0 configuration style is still 100% valid configuration; under the covers think of the new <tx:tags/gt; as simply defining TransactionProxyFactoryBean beans on your behalf. This is how I got it to work: Although I couldn't find that AppFuse is using AspectJ, everything works fine, when AspectJ is enabled. The Spring Reference Documentation, Version 2.0, Chapter 6.2.1. describes two ways to do so: <aop:aspectj-autoproxy/> <bean class="org.springframework.aop.aspectj.annotation.AnnotationAwareAspectJAutoProxyCreator" /> If I change my applicationContext-service.xml to contain the second signature, database write operations work fine. That rises two questions Why is AspectJ required in my application, but not in a clean AppFuse 1.9.4 application? For me it seems as if applicationContext-service.xml is using the schema notation, but the working signature is a dtd notation? -- View this message in context: http://www.nabble.com/Problems-with-HibernateTransactionManager%2C-FlushMode%2C-readOnly-when-upgrading-from-Appfuse-1.9.3-to-1.9.4-tf2772668s2369.html#a7754306 Sent from the AppFuse - User mailing list archive at Nabble.com.
