mirror of
https://github.com/hibernate/hibernate-orm
synced 2025-02-17 08:35:13 +00:00
Update doc with hilo inside JTA
git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@5716 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
parent
8f557f26ff
commit
d50b32d0e0
@ -747,7 +747,7 @@
|
||||
</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="mapping-declaration-id-hilo">
|
||||
<sect3 id="mapping-declaration-id-hilo" revision="1">
|
||||
<title>Hi/lo algorithm</title>
|
||||
<para>
|
||||
The <literal>hilo</literal> and <literal>seqhilo</literal> generators provide two alternate
|
||||
@ -773,10 +773,9 @@
|
||||
|
||||
<para>
|
||||
Unfortunately, you can't use <literal>hilo</literal> when supplying your own
|
||||
<literal>Connection</literal> 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.
|
||||
<literal>Connection</literal> to Hibernate. When Hibernate is using an application
|
||||
server datasource to obtain connections enlisted with JTA, you must properly configure
|
||||
the <literal>hibernate.transaction.manager_lookup_class</literal>.
|
||||
</para>
|
||||
</sect3>
|
||||
|
||||
|
@ -812,7 +812,7 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]></programlisting>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<table frame="topbot" id="configuration-transaction-properties" revision="7">
|
||||
<table frame="topbot" id="configuration-transaction-properties" revision="8">
|
||||
<title>Hibernate Transaction Properties</title>
|
||||
<tgroup cols="2">
|
||||
<colspec colname="c1" colwidth="1*"/>
|
||||
@ -858,7 +858,8 @@ hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect]]></programlisting>
|
||||
</entry>
|
||||
<entry>
|
||||
The classname of a <literal>TransactionManagerLookup</literal>
|
||||
- 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.
|
||||
<para>
|
||||
<emphasis role="strong">eg.</emphasis>
|
||||
<literal>classname.of.TransactionManagerLookup</literal>
|
||||
|
Loading…
x
Reference in New Issue
Block a user