HHH-13125 - Remove the Javadoc links in the User Guide pointing internal classes

This commit is contained in:
Vlad Mihalcea 2018-11-27 13:45:00 +02:00 committed by Guillaume Smet
parent 1b53969359
commit d48307d5fa
2 changed files with 2 additions and 4 deletions

View File

@ -32,7 +32,7 @@ Supply a custom strategy for the scoping of the _current_ `Session`.
+
The definition of what exactly _current_ means is controlled by the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/context/spi/CurrentSessionContext.html[`CurrentSessionContext`] implementation in use.
+
Note that for backward compatibility, if a https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/context/spi/CurrentSessionContext.html[`CurrentSessionContext`] is not configured but JTA is configured this will default to the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/context/internal/JTASessionContext.html[`JTASessionContext`].
Note that for backward compatibility, if a `CurrentSessionContext` is not configured but JTA is configured this will default to the `JTASessionContext`.
[[configurations-jpa-compliance]]
=== JPA compliance
@ -893,7 +893,7 @@ Valid options are defined by the `strategy` value of the https://docs.jboss.org/
Identifies the delimiter to use to separate schema management statements in script outputs.
`*hibernate.schema_management_tool*` (e.g. A schema name)::
Used to specify the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/tool/schema/spi/SchemaManagementTool.html[`SchemaManagementTool`] to use for performing schema management. The default is to use https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/tool/schema/internal/HibernateSchemaManagementTool.html[`HibernateSchemaManagementTool`]
Used to specify the `SchemaManagementTool` to use for performing schema management. The default is to use `HibernateSchemaManagementTool`.
`*hibernate.synonyms*` (e.g. `true` or `false` (default value))::
If enabled, allows schema update and validation to support synonyms. Due to the possibility that this would return duplicate tables (especially in Oracle), this is disabled by default.

View File

@ -166,13 +166,11 @@ Out-of-the-box, Hibernate comes with three implementations of this interface:
`org.hibernate.context.internal.JTASessionContext`::
current sessions are tracked and scoped by a `JTA` transaction.
The processing here is exactly the same as in the older JTA-only approach.
See the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/context/internal/JTASessionContext.html[Javadocs] for more details.
`org.hibernate.context.internal.ThreadLocalSessionContext`::
current sessions are tracked by thread of execution. See the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/context/internal/ThreadLocalSessionContext.html[Javadocs] for more details.
`org.hibernate.context.internal.ManagedSessionContext`::
current sessions are tracked by thread of execution.
However, you are responsible to bind and unbind a `Session` instance with static methods on this class; it does not open, flush, or close a `Session`.
See the https://docs.jboss.org/hibernate/orm/{majorMinorVersion}/javadocs/org/hibernate/context/internal/ManagedSessionContext.html[Javadocs] for details.
Typically, the value of this parameter would just name the implementation class to use.
For the three out-of-the-box implementations, however, there are three corresponding short names: _jta_, _thread_, and _managed_.