I have Spring Data REST repository that takes query parameters. It uses a PagingAndSortingRepository and looks like this:<\/p>\n
[code language=”java”]
\n@RepositoryRestResource
\n@CrossOrigin(origins = "http:\/\/localhost:8000")
\npublic interface IRestaurantRepository extends PagingAndSortingRepository<Restaurant, Long> {
\n\tpublic Page<Restaurant> findByNameContaining(String name, Pageable pageable);<\/p>\n
}
\n[\/code]<\/p>\n
You would get an error if you were to execute the search command that is created for you with cURL.<\/p>\n
[code language=”bash”]
\n$ curl -X GET http:\/\/localhost:8181\/restaurants\/search\/findByNameContaining?name=Foo
\n{"cause":null,"message":"Unable to detect parameter names for query method com.coysoft.wingspecial.repository.IRestaurantRepository.findByNameContaining! Use @Param or compile with -parameters on JDK 8."}
\n[\/code]<\/p>\n
The error is pretty useful. It gives us two options for being able to use query parameters. The first is straightforward. Just modify the code like so:<\/p>\n
[code language=”java”]
\n@RepositoryRestResource
\n@CrossOrigin(origins = "http:\/\/localhost:8000")
\npublic interface IRestaurantRepository extends PagingAndSortingRepository<Restaurant, Long> {
\n\tpublic Page<Restaurant> findByNameContaining(@Param("name") String name, Pageable pageable);<\/p>\n
}
\n[\/code]<\/p>\n
With this modification you’ll be able to get results. The second option involves modifying your build process. In my case, I am using Maven and I am in fact using Java 8. Therefore, I can modify the pom.xml to use this:<\/p>\n
[code language=”xml” highlight=”16″]
\n\t<build>
\n\t\t<plugins>
\n\t\t\t<plugin>
\n\t\t\t\t<groupId>org.springframework.boot<\/groupId>
\n\t\t\t\t<artifactId>spring-boot-maven-plugin<\/artifactId>
\n\t\t\t<\/plugin>
\n\t\t\t<plugin>
\n\t\t\t\t<groupId>org.apache.maven.plugins<\/groupId>
\n\t\t\t\t<artifactId>maven-compiler-plugin<\/artifactId>
\n\t\t\t\t<version>3.3<\/version>
\n\t\t\t\t<configuration>
\n\t\t\t\t\t<source>1.8<\/source>
\n\t\t\t\t\t<target>1.8<\/target>
\n\t\t\t\t\t<fork>true<\/fork>
\n\t\t\t\t\t<compilerArgs>
\n\t\t\t\t\t\t<arg>-parameters<\/arg>
\n\t\t\t\t\t<\/compilerArgs>
\n\t\t\t\t<\/configuration>
\n\t\t\t<\/plugin>
\n\t\t<\/plugins>
\n\t\t<finalName>ROOT<\/finalName>
\n\t<\/build><\/p>\n
[\/code]<\/p>\n
Both work the same for me. Using @Param is more backwards compatible and verbose, but using -parameters would work across the board.<\/p>\n","protected":false},"excerpt":{"rendered":"
I have Spring Data REST repository that takes query parameters. It uses a PagingAndSortingRepository and looks like this: [code language=”java”] @RepositoryRestResource @CrossOrigin(origins = "http:\/\/localhost:8000") public interface IRestaurantRepository extends PagingAndSortingRepository<Restaurant, Long> { public Page<Restaurant> findByNameContaining(String name, Pageable pageable); } [\/code] You would get an error if you were to execute the…<\/p>\n