diff --git a/reference/en/modules/basic_mapping.xml b/reference/en/modules/basic_mapping.xml index 33b50c1700..eee26f86b1 100644 --- a/reference/en/modules/basic_mapping.xml +++ b/reference/en/modules/basic_mapping.xml @@ -747,7 +747,7 @@ - + Hi/lo algorithm The hilo and seqhilo generators provide two alternate @@ -773,10 +773,9 @@ Unfortunately, you can't use hilo when supplying your own - Connection to Hibernate, or when Hibernate is using an application - server datasource to obtain connections enlisted with JTA. Hibernate must be able to - fetch the "hi" value in a new transaction. A standard approach in an EJB environment is - to implement the hi/lo algorithm using a stateless session bean. + Connection to Hibernate. When Hibernate is using an application + server datasource to obtain connections enlisted with JTA, you must properly configure + the hibernate.transaction.manager_lookup_class. diff --git a/reference/en/modules/configuration.xml b/reference/en/modules/configuration.xml index e22f491527..631ff42451 100644 --- a/reference/en/modules/configuration.xml +++ b/reference/en/modules/configuration.xml @@ -812,7 +812,7 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]> - +
Hibernate Transaction Properties @@ -858,7 +858,8 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]> The classname of a TransactionManagerLookup - - required when JVM-level caching is enabled in a JTA environment. + - required when JVM-level caching is enabled or when using hilo + generator in a JTA environment. eg. classname.of.TransactionManagerLookup