From be5946d55ac7d4e266b4a2568788b41895ef5fe7 Mon Sep 17 00:00:00 2001 From: Oliver Gierke Date: Wed, 17 May 2017 07:13:44 +0200 Subject: [PATCH] DATAJPA-1086 - Improved exception message in StringQuery in case of undetectable parameter names. We now explicitly hint at compiling with -parameters on JDK 8 to use named parameters. --- .../springframework/data/jpa/repository/query/StringQuery.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/java/org/springframework/data/jpa/repository/query/StringQuery.java b/src/main/java/org/springframework/data/jpa/repository/query/StringQuery.java index 1f612e45a..285d41439 100644 --- a/src/main/java/org/springframework/data/jpa/repository/query/StringQuery.java +++ b/src/main/java/org/springframework/data/jpa/repository/query/StringQuery.java @@ -41,7 +41,7 @@ import org.springframework.util.StringUtils; */ class StringQuery { - private static final String PARAMETER_NAME_MISSING = "Name for parameter binding must not be null or empty! For named parameters you need to use @Param for query method parameters on Java versions < 8."; + private static final String PARAMETER_NAME_MISSING = "Name for parameter binding must not be null or empty! On JDKs < 8, you need to use @Param for named parameters, on JDK 8 or better, be sure to compile with -parameters."; private final String query; private final List bindings;