From bd4c8082f39e8494232cd09a96680c6b8b8b3bdc Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Tue, 16 Sep 2025 16:45:58 +0200 Subject: [PATCH] Remove `EntityInformation` customization from Entity State Detection Strategies. Customizing EntityInformation has only a single use-case within JPA. All other modules should use customization using the mentioned mechanisms as the underlying MappingContext handles typically IsNew detection but customizing the MappingContext (PersistentEntity) is a deeply involved task. Closes #3364 --- .../antora/modules/ROOT/pages/is-new-state-detection.adoc | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/main/antora/modules/ROOT/pages/is-new-state-detection.adoc b/src/main/antora/modules/ROOT/pages/is-new-state-detection.adoc index f37b9cd4d..545b6f364 100644 --- a/src/main/antora/modules/ROOT/pages/is-new-state-detection.adoc +++ b/src/main/antora/modules/ROOT/pages/is-new-state-detection.adoc @@ -23,8 +23,4 @@ See the {spring-data-commons-javadoc-base}/org/springframework/data/domain/Persi _Note: Properties of `Persistable` will get detected and persisted if you use `AccessType.PROPERTY`. To avoid that, use `@Transient`._ -|Providing a custom `EntityInformation` implementation -|You can customize the `EntityInformation` abstraction used in the repository base implementation by creating a subclass of the module specific repository factory and overriding the `getEntityInformation(…)` method. -You then have to register the custom implementation of module specific repository factory as a Spring bean. -Note that this should rarely be necessary. |===