The docs for the EntityManager say, that setDatasource() on an Ejb3Configuration is ignored outside an ApplicationServer, which means that this:




silently fails outside an app-server.

I'm trying to use the EntityManager outside an appserver and have configured DataSources via Spring using




So, two questions:
- I am outside of an appserver, but I have a DataSource - how can I teach hibernate to use the supplied DataSource?
- can I trick Hibernate to think that its inside an Appserver? Or more precise, how does hibernate determine if it lives inside an Appserver?

At least a message, that the setDataSource() is ignored would be nice - right now the method fails silently. It would be nice to add a warning...

cheers
stf

In the current implementation, you'll need to add in the properties


In CVS, HEM tries to set it when the datasource is set, so unless the user override this property, it should work out of the box.

PS: there is no such statement in the HEM doc. What is said is that the jta-data-source property (ie it's JNDI name) is ignored outside a container wich make sense since you don't have any JNDI and Datasource at your disposal. I've updated the JavaDoc to reflect that idea.

Thx! Using the hibernate.connection.provider_class-property, hibernate now takes the externally injected DataSource.

There is only one problem left, but this may be a Spring-Problem: We're using a org.springframework.jdbc.datasource.DataSourceTransactionManager to manage the Transactions on the injected datasource. We just make getTransaction()/commit()-calls on this TransactionManager to begin and end our transaction, but these Transactions are obviuously not enough for the EntityManager - it still complains, that no transaction is running - is it necessary to call getEntityManager().getTransaction().begin(); to get the EntityManager to recognize a running transaction or has the EM other means to find out that a transaction is already running?


[/code]

Yes getTx().begin() is mandatory. Be careful em.getTransaction() is not the Hibernate transaction API. It only relies on the resource transaction, not the JTA one.