From 289f3f9e514fa5159efa5bd364b1dd63344be4a8 Mon Sep 17 00:00:00 2001 From: Scott Frederick Date: Fri, 3 May 2024 10:46:38 -0500 Subject: [PATCH] Polish "Add How-To documentation for ManagedClassNameFilter" See gh-40617 --- .../src/docs/antora/modules/how-to/pages/data-access.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc index 0ece8a00a5..471724ec90 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc @@ -178,9 +178,9 @@ include-code::MyApplication[] [[howto.data-access.filter-scanned-entity-definitions]] -== Filter scanned @Entity definitions +== Filter Scanned @Entity Definitions -It is possible to exclude some `@Entity` definitions using a `ManagedClassNameFilter` bean. +It is possible to filter the `@Entity` definitions using a `ManagedClassNameFilter` bean. This can be useful in tests when only a sub-set of the available entities should be considered. In the following example, only entities from the `com.example.app.customer` package are included: