Atomikos Forum

The javadoc of com.atomikos.icatch.jta.hibernate3.AtomikosJTATransactionFactory states...

Atomikos-specific JTATransactionFactory implementation that does not rely on JNDI for standalone (JNDI-less) deployments.

However case 32252 has led to...

public void configure(Properties props) throws HibernateException {
 //fix for case 32252: hibernate config init
  super.configure ( props );
}

and super.configure() relies on... JNDI!

If you leave out this "fix" and don't override "configure" at all everything seems to work fine and you don't get JNDI related exceptions.

So what will you do? Change the Javadoc? Change the code? If it is your intention to force the use of JNDI then I would like some pom.xml concerning needed dependencies.

Thanks!

Little mistake: you *should* override configure but with an empty body.

Hi,

The Hibernate/JNDI problem is a known one, so I have added your suggestion to the case. What release of Hibernate did you try this with?

Thanks
Guy

We use the 3.3.1.GA version of hibernate-core. However, I have checked the hibernate svn trunk and I can see the dependency on JNDI there too. So I don't think a switch of version will do the trick.

OK, I was afraid of that. Like I said, we'll try to get this fixed on our end then.

I was also looking at other solutions today, and it seems like Spring's LocalSessionFactory also has a setJtaTransactionManager injector method. Might be an alternative?