[hibernate-commits] [hibernate/hibernate-orm] f4f1bb: improve two exception messages

Branch: refs/heads/main Home: https://github.com/hibernate/hibernate-orm Commit: f4f1bbe1d0ce561d0c1b6b31087e7c5cdecd8eae https://github.com/hibernate/hibernate-orm/commit/f4f1bbe1d0ce561d0c1b6b3... Author: Gavin King <gavin(a)hibernate.org&gt; Date: 2026-02-08 (Sun, 08 Feb 2026) Changed paths: M hibernate-core/src/main/java/org/hibernate/BatchSize.java M hibernate-core/src/main/java/org/hibernate/metamodel/model/domain/internal/AbstractManagedType.java Log Message: ----------- improve two exception messages Commit: 773e14e098dc0bb5ca79d1fb64c2a79b52a8de88 https://github.com/hibernate/hibernate-orm/commit/773e14e098dc0bb5ca79d1f... Author: Gavin King <gavin(a)hibernate.org&gt; Date: 2026-02-08 (Sun, 08 Feb 2026) Changed paths: M hibernate-core/src/main/java/org/hibernate/boot/model/internal/InheritanceState.java A hibernate-core/src/test/java/org/hibernate/orm/test/mapping/access/AccessTypeTest.java Log Message: ----------- HHH-18529 fix access type determination Fix for subclasses which inherit a @MappedSuperclass with an explicit access type. @Access is not supposed to be inherited, and this behavior caused Hibernate to ignore persistent fields of subclasses. in order to preserve a reasonable degree of backward compatibility, I have introduced an access type "search" algorithm which is not really very well-founded in the spec itself, but seems reasonably natural, and seems to do a reasonable job of reproducing the very ad hoc legacy behavior. Compare: https://github.com/hibernate/hibernate-orm/compare/c4efb0c009e6...773e14e... To unsubscribe from these emails, change your notification settings at https://github.com/hibernate/hibernate-orm/settings/notifications