HHH-10006 - Document configuration of JndiService

This commit is contained in:
Steve Ebersole 2015-07-31 09:26:50 -05:00
parent 8f4c2d5182
commit c1af6433c2
3 changed files with 11 additions and 8 deletions

View File

@ -78,11 +78,8 @@
Hibernate can integrate with a <interfacename>javax.sql.DataSource</interfacename> for obtaining
JDBC Connections. Applications would tell Hibernate about the DataSource via the (required)
<literal>hibernate.connection.datasource</literal> setting which can either specify a JNDI name
or would reference the actual DataSource instance.
<!-- todo : pointer to JndiService
For cases where a JNDI namespace is specified, be
sure to read <xref linkend="bootstrap-jndi"/>.-->
or would reference the actual DataSource instance. For cases where a JNDI name is given, be sure
to read <xref linkend="jndi"/>
</para>
<note>

View File

@ -5,7 +5,7 @@
~ License: GNU Lesser General Public License (LGPL), version 2.1 or later.
~ See the lgpl.txt file in the root directory or <http://www.gnu.org/licenses/lgpl-2.1.html>.
-->
<chapter xml:id="JNDI.xml"
<chapter xml:id="jndi"
xml:lang="en"
xmlns="http://docbook.org/ns/docbook">
<title>JNDI</title>

View File

@ -100,8 +100,6 @@
<section xml:id="transactions-physical-jtaplatform">
<title>JTA configuration</title>
<!-- todo : pointer to JndiService -->
<para>
Interaction with a JTA system is consolidated behind a single contract named
<interfacename>org.hibernate.engine.transaction.jta.platform.spi.JtaPlatform</interfacename> which
@ -111,6 +109,14 @@
check transaction status, etc.
</para>
<note>
<para>
Generally JtaPlatform will need access to JNDI to resolve the JTA TransactionManager,
UserTransaction, etc. See <xref linkend="jndi"/> for details on configuring access
to JNDI
</para>
</note>
<para>
Hibernate tries to discover the JtaPlatform it should use through the use of another service named
<interfacename>org.hibernate.engine.transaction.jta.platform.spi.JtaPlatformResolver</interfacename>.