Skip to content

HHH-19446 HHH-18633 hibernate-scan-jandex migration guide #10285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 10, 2025
Merged

HHH-19446 HHH-18633 hibernate-scan-jandex migration guide #10285

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions migration-guide.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -627,6 +627,13 @@ specify a name for JNDI binding. The new behavior is as follows (assuming `hibe
Hibernate can use the persistence-unit name for binding into JNDI as well, but `hibernate.session_factory_name_is_jndi`
must be explicitly set to true.

[[jandex-scanning]]
=== Entity Discovery

Entity discovery, i.e. automatic detection of mapped Java classes through classpath scanning, now requires by default the new `hibernate-scan-jandex` module. Standalone Hibernate ORM applications relying on this feature will need to add a dependency to this new module in order to continue using it.

Users can still provide custom `org.hibernate.Scanner` implementations via the `org.hibernate.boot.archive.scan.spi.ScannerFactory` service or the `hibernate.archive.scanner` configuration parameter.

[[unowned-order-column]]
=== @OrderColumn in Unowned @OneToMany Associations

Expand Down