Does hibernate2.1rc1 ALWAYS require you to specify hibernate.transaction.manager_lookup_class when using JVM-level caching? Only in a JTA environment? Or even when using JDBC connections/transactions?

The on-line documentation (Section 3.5, Table 3.3) seems to indicate only when JVM-level caching is enabled in a JTA environment. But the Hibernate changelog says "ALWAYS" when using JCS caching, and that the JTA TransactionManager is now used even when not using Hibernate Transaction API.

If it is ALWAYS required, I assume it's not specific to JCS caching, but any JVM-level caching (regardless of which cache provider is being used).

Thanks for the clarification!

Sarah

You should always specify hibernate.transaction.manager_lookup_class when using JVM-level caching in a JTA environment. :)