spring-transactions

I have a doubt related to transactions within transactions. For background, I have a School entity object which has Set of Students entity object mapped to it. I am using Spring Data JPA which is taking care of all the crud operations. I have a SchoolManagementService class which has @Transactional(readonly=true) set at the class level and for all updating methods I am using @Transactional over them. In my SchoolManagementService class I have a method deleteStudents(List) which I have marked as @Transactional. In this method I am calling StudentsRepository.delete(studentId) again and again. I

There is a Websphere AS 8.5 where runs XA Datasource. Also there is a Spring application which must work in this environment and connect to the datasource. An application context is loaded by a servlet and the application uses RmiExporters to provide RMI access to some services (which are shared in the separate thread) and all DAOs' methods are marked with @Transactional . If I try to write something to the database from the main thread (e.g. during initialization of any class), it works properly. But if I try to write (or read with HQL SELECT-query) something via RMI invokation I see an

I am migrating a legacy Spring 3, Hibernate 3, JTA on JBoss 5 application to the latest versions (Spring 4.1.0.RELEASE, Hibernate 4.3.6.Final, JBoss Wildfly 8.1). It seems that Spring 4.1.0.RELEASE and Hibernate 4.3.6.Final do NOT work together in supporting transactions for write operations with the LocalSessionFactoryBean and the HibernateTransactionManager as configured below. Read-only get operations appear to be working ok. To migrate, org.springframework.orm. hibernate3 .support.HibernateDaoSupport has been updated to org.springframework.orm. hibernate4 .support.HibernateDaoSupport. The

I've seen a lot of similar questions but they are usually just tangential to mine. Here is my code. @Override //class implements interface //can also add "rollbackFor = OutOfMemoryError.class" here, to no avail @Transactional(noRollbackFor = IllegalArgumentException.class) public ReportTemplate getByCode(final String code) //throws IllegalArgumentException - see question text { if(code == null) { throw new IllegalArgumentException("ss"); } } Consumer (non-transactional) calls this method via autowired interface. Despite noRollbackFor the transaction (consisting of this method alone) gets

I would like to get some clarification regarding lazy loading and session boundaries etc. My code structure is as follows @Entity class A { .... @OneToOne(fetch=LAZY) private B b; .. } @Entity class B { private id; private name; } @Transactional(SUPPORTS) ADao { A findById(int id); } @Transactional(SUPPORTS) LayerDB { A getAForId(int i) { return adao.findById(i); } } //Note that there is no transactional attribute here LayerB { public boolean doSomethingWithAandB(int aId) { A a = LayerDB.getAForId(aId); if(a.getB().getName().equals("HIGH")) return true; return false; } } //start transaction

Does spring boot automatically add @Transactional annotation at controller layer? I tried putting @Transactional at service layer but it seems that the controller layer is overriding the annotation. I have this config <tx:advice id="txAdvice" transaction-manager="transactionManager"> <tx:attributes> <tx:method name="find*" read-only="true" isolation="READ_COMMITTED" propagation="NOT_SUPPORTED" /> <tx:method name="load*" read-only="true" isolation="READ_COMMITTED" propagation="NOT_SUPPORTED" /> <tx:method name="get*" read-only="true" isolation="READ_COMMITTED" propagation="NOT_SUPPORTED" /> <tx

I don't get why this integration test fails. I can get the test to pass by either removing the @Transactional(propagation = Propagation.REQUIRES_NEW) annotation above the service method, OR by setting transactional = false in the Integration Test I realize that the integration test itself is running in a transaction, and that's why I've got the annotation on the service method. class DbTests extends GrailsUnitTestCase { boolean transactional = true def customerService void testTransactionsCommit() { def orderIds = [1, 2, 3] orderIds.each { // lets make sure they all start out as Active def