diff --git a/jpa/pom.xml b/jpa/pom.xml index 28cbfdbc..bf7ef47b 100644 --- a/jpa/pom.xml +++ b/jpa/pom.xml @@ -23,16 +23,12 @@ java8 javaslang jpa21 - + security multiple-datasources eclipselink query-by-example - - 5.2.7.Final - - diff --git a/jpa/security/src/main/java/example/springdata/jpa/security/SecureBusinessObjectRepository.java b/jpa/security/src/main/java/example/springdata/jpa/security/SecureBusinessObjectRepository.java index 20102058..9b2dbb90 100644 --- a/jpa/security/src/main/java/example/springdata/jpa/security/SecureBusinessObjectRepository.java +++ b/jpa/security/src/main/java/example/springdata/jpa/security/SecureBusinessObjectRepository.java @@ -28,18 +28,12 @@ import org.springframework.data.repository.Repository; interface SecureBusinessObjectRepository extends Repository { /** - * Here we demonstrate the usage of SpEL expression within a custom query. - * With the {@link example.springdata.jpa.security.SecurityEvaluationContextExtension} in place - * we can safely access auth information provided by the Spring Security Context. - * - * The Spring Data Repository infrastructure will translate the given query string into the - * parameterized form: - * - * + * Here we demonstrate the usage of SpEL expression within a custom query. With the + * {@link example.springdata.jpa.security.SecurityEvaluationContextExtension} in place we can safely access auth + * information provided by the Spring Security Context. The Spring Data Repository infrastructure will translate the + * given query string into the parameterized form: * select o from BusinessObject o where o.owner.emailAddress like ? - * - * - * and set the the result SpEL expression evaluated at method invocation time as parameter value. + * and set the the result SpEL expression evaluated at method invocation time as parameter value. * * @return */ @@ -57,7 +51,7 @@ interface SecureBusinessObjectRepository extends Repository