jta

I am using Hibernate to do my ORM stuff w/ HSQL for tests. It seems that a connection is fetched to do the insert and then returned. Straight after that HIbernate gets a connection then tries to fetch the identity from HSQL but that returns 0 which is obviously wrong. WHen i was running w/out a tm and datasource using a plain pooled connection everything worked but with the new tm + ds i am getting this problem. The answer is the DataSource should be tx aware, so that connections are sticky for each new tx. The original problem was a different connection was used to fetch the identity of the

I'm developing in a JavaEE environment (weblogic 12), and part of my code uses JDBC; Therefore, I need to aqcuire a JDBC connection from the application server. I know it's a really bad practice to use JDBC in JavaEE, but that's a code I cannot change (legacy). I've found a way to do it, but I'm not sure it's the right way: @Resource(mappedName="mydsjndipath") private DataSource ds; public void foo() { Connection conn = ds.getConnection(); } The question is what do I do with the connection at the end? I can't really commit/rollback it, because I use a distributed transaction. But should I at

I have a problem. I am working on java application server(sap netweaver) with I am using ejb 3.0 So I want to database insert one by one. Because I have too much data and i have to divide data. So I made try test code and it did work but it did not work as I want. I want to create a new transaction for each part and of course at the end method(transaction) should be commit. Sample code is below; package com.transaction.jobs; import javax.ejb.Local; /** * * @author muratdemir */ @Local public interface TestTransactionLocal { public void onStart(); public void insertObject(int i); } and package

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 have a hibernate application which directly uses Java Transaction API resources. I'm trying to use UserTransaction to accomplish some basic database transactions The UserTransaction interface defines the methods that allow an application to explicitly manage transaction boundaries In hibernate.cfg.xml file I have the following properties: <session-factory> <property name="show_sql">true</property> <property name="connection.datasource">java:comp/env/myDataSource</property> <property name="jta.UserTransaction">java:comp/UserTransaction</property> <property name="transaction.factory_class">org

I am learning spring 3.0 from Spring in Action. There it talks about importance of having jpadialect in JpaTranactionManager <bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager"> <property name="entityManagerFactory" ref="entityManagerFactory" /> <property name="jpaDialect" ref="jpaDialect" /> </bean> <bean id="jpaDialect" class="org.springframework.orm.jpa.vendor.HibernateJpaDialect" /> However the dialect is already present in declaration of entityManagerFactory via jpaVendorAdaptor. <bean id="entityManagerFactory" class= "org.springframework.orm.jpa