From df04b0253f380a031a82a949777890a13e0717c3 Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Tue, 3 Dec 2024 10:29:29 +0100 Subject: [PATCH] Polishing. Tweak wording. See: #3286 Original pull request: #3449 --- .../antora/modules/ROOT/pages/repositories/projections.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/main/antora/modules/ROOT/pages/repositories/projections.adoc b/src/main/antora/modules/ROOT/pages/repositories/projections.adoc index 04ad285e4..3c6bca832 100644 --- a/src/main/antora/modules/ROOT/pages/repositories/projections.adoc +++ b/src/main/antora/modules/ROOT/pages/repositories/projections.adoc @@ -18,8 +18,9 @@ include::{commons}@data-commons::page$repositories/projections-class.adoc[levelo [NOTE] ==== -Some JPA providers may require additional hints when working with <> especially when using those directly with method derived queries. -If you are facing errors like `JpaSystemException: Specified result type did not match Query selection type` make sure to provide a constructor hint via `@PersistenceCreator` to be passed on, as outlined below: +<> types must declare a single constructor so that Spring Data can determine its input properties. +If your class defines more than one constructor, then you cannot use the type without further hints for DTO projections. +In such a case annotate the desired constructor with `@PersistenceCreator` as outlined below so that Spring Data can determine which properties to select: [source,java] ----