Prep for 7.1

Author: sebersole

migration-guide.adoc

@@ -45,7 +45,7 @@ This section describes changes to contracts (classes, interfaces, methods, etc.)
 
 7.0 begins the process of reducing the visibility of `org.hibernate.LockOptions`.
 This class was originally exposed as an API, even though it is more properly an SPI.
-From an API perspective, `FindOption`, `LockOption` and `RefreshOption` are much better ways to specify that information.
+From an API perspective, `FindOption`, `LockOption` and `RefreshOption` are much better ways to specify this information.
 The class itself, as well as API methods which expose it, have been deprecated.
 
 However, 2 aspects of `LockOptions` have been completely removed.
@@ -90,12 +90,76 @@ Applications should instead manage both sides of such associations directly as w
 Second is a little-known feature called "extended" enhancement.
 Applications should instead use proper object-oriented encapsulation, exposing managed state via getters and setters.
 
+Additionally, attempting to re-enhance a class with different options is no longer allowed and will result in a `FeatureMismatchException`.
+
 
 [[session-getLobHelper]]
 === Session#getLobHelper
 
 The `Session#getLobHelper` method has been marked as deprecated in favor of the static `Hibernate#getLobHelper` and will be removed in a future *major* version.
 
+[[H2-lock-timeout]]
+=== WAIT, NO WAIT and SKIP LOCKED for H2
+
+The for-update clause enhancements of H2 2.2.220 are now reflected in the Hibernate ORM dialect, allowing applications to use `wait`, `no wait` and `skip locked` options.
+
+
+// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+// SPI changes
+// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+[[spi-changes]]
+== Changes to SPI
+
+[[force-increment]]
+=== Force-increment Locking for Version with Custom Generator
+
+A new event type (`FORCE_INCREMENT`) has been added to
+`org.hibernate.generator.EventType` to support
+`OPTIMISTIC_FORCE_INCREMENT` and `PESSIMISTIC_FORCE_INCREMENT`
+when used with `@Version` mappings with custom generators.
+
+
+[[pessimistic-locking]]
+=== Pessimistic Locking
+
+A number of changes have been made to pessimistic locking support.
+
+* Introduction of `org.hibernate.dialect.lock.spi.LockingSupport` which represents a Dialect's support for pessimistic locking.
+* Introduction of `org.hibernate.sql.ast.spi.LockingClauseStrategy` to integrate into SQL AST translation.
+* Changed standard implementation of `org.hibernate.dialect.lock.LockingStrategy` for pessimistic locking to one using SQL AST.
+* Changes to `LockOptions` as <<lock-options,already discussed>>.
+
+[NOTE]
+More changes related to pessimistic locking are coming in later 7.x releases.
+We've opted to tackle these in stages since they all relate and build on top of each other.
+See https://hibernate.atlassian.net/browse/HHH-19551 for details.
+
+[[format-mapper]]
+=== JSON FormatMapper Enhancements
+
+JSON mappings on Oracle 21+ will now try to leverage driver built-in OSON decoding to improve JSON parsing performance. In case of trouble, this can be disabled with the `hibernate.dialect.oracle.oson_format_disabled` configuration option.
+
+
+[[enhancement-option-granularity]]
+=== Enhancement Option Granularity
+
+The actual enhancements written into bytecode were previously allowed to vary by class and sometimes even by attribute.
+However, all Hibernate tooling only supported setting those "globally" per enhancement.
+To this end, all `org.hibernate.bytecode.enhance.spi.EnhancementContext` methods which determine whether certain aspects of enhancement are applied have changed to no longer accept class/attribute.
+Specifically:
+
+* `doDirtyCheckingInline(UnloadedClass classDescriptor)` -> `doDirtyCheckingInline()`
+* `doExtendedEnhancement(UnloadedClass classDescriptor)` -> `doExtendedEnhancement()`
+* `doBiDirectionalAssociationManagement(UnloadedField field)` -> `doBiDirectionalAssociationManagement()`
+
+See also <<enhancement-options>>.
+
+
+// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+// DDL changes
+// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 [[ddl-changes]]
 == Changes to DDL generation
 

whats-new.adoc

@@ -10,7 +10,33 @@ Describes the new features and capabilities added to Hibernate ORM in 7.1.
 
 If migrating from earlier versions, be sure to also check out the link:{migrationGuide}[Migration Guide] for discussion of impactful changes.
 
-[[Teradata]]
-== TeradataDialect
 
-7.1 adds a Dialect for the Teradata database, supporting version 12 and higher.
+[[resource-discovery]]
+== Resource Discovery in SE Environments
+
+The Jakarta Persistence specification defines the ability for a provider to discover "managed resources" in EE environments, alleviating the application from manually listing all classes and XML files.
+However, it defines no such support in SE environments.
+
+Starting with 7.1, Hibernate now supports this discovery in SE environments, by allowing applications to specify the root URL and zero-or-more "jar" URLs to search.
+These URLs correspond to
+
+* `jakarta.persistence.spi.PersistenceUnitInfo#getPersistenceUnitRootUrl`
+* `jakarta.persistence.spi.PersistenceUnitInfo#getJarFileUrls`
+
+These URLs are searched for managed resources according to the process defined in https://jakarta.ee/specifications/persistence/3.2/jakarta-persistence-spec-3.2#a12305[the specification].
+
+[[locking]]
+== Locking
+
+`org.hibernate.Locking` has been introduced to support various aspects of pessimistic locking:
+
+* `Locking.Scope` is an extension of `jakarta.persistence.PessimisticLockScope` including some Hibernate-specific options.
+* `Locking.FollowOn` allows controlling Hibernate's follow-on locking behavior.
+
+Additionally, we've added `org.hibernate.Timeouts` to help deal with some standard `jakarta.persistence.Timeout` values.
+
+
+[[interceptor-merge]]
+== Interceptor and merge
+
+Support for intercepting `Session#merge` events has been added to Hibernate's `Interceptor`.