spring-hateoas

I am currently building an application with a REST interface, using Spring Boot, Hibernate and Spring-HATEOAS. My data model is defined as beans with @Entity annotation and I am using Spring's feature to automatically set up a Hibernate repository (Creating an interface extending PagingAndSortingRepository ). My application is completely annotation-driven, i.e., I have no web.xml but configure everything with the Spring annotations like @Configuration , @Bean etc., and start the application from my main method with the help of SpringApplication.run(MyApp.class, args); This works fine, but with

I'm using Spring Boot and HATEOAS to build a REST API and when my API returns a collection, it is wrapped inside a "_embedded" property, like so: { "_links":{ "self":{ "href":"http://localhost:8080/technologies" } }, "_embedded":{ "technologies":[ { "id":1, "description":"A", "_links":{ "self":{ "href":"http://localhost:8080/technologies/1" } } }, { "id":2, "description":"B", "_links":{ "self":{ "href":"http://localhost:8080/technologies/2" } } } ] } } I want the response to be like this: { "_links":{ "self":{ "href":"http://localhost:8080/technologies" } }, "technologies":[ { "id":1,

I have a Spring Data Rest Repository controller that utilizes JPA for the query implementation, and I need to add some custom query methods that cannot be done using the standard queryByExample method that JPA supports. I have created an Impl class that has the necessary method, but I cannot get it to be recognized. I saw that I can utilize a standard Spring MVC Controller, but I want to have a unified API, and basically all I really want is to implement my own custom /search methods. Even with the custom controller, the problem is then that the HAL links and other related items are no longer

Question. How do I avoid n+1 queries with Spring Data REST? Background. When querying Spring Data REST for a list of resources, each of the resulting top-level resources has links to the associated resources, as opposed to having the associated resources embedded directly in the top-level resources. For example, if I query for a list of data centers, the associated regions appear as links, like this: { "links" : [ { "rel" : "self", "href" : "http://localhost:2112/api/datacenters/1" }, { "rel" : "datacenters.DataCenter.region", "href" : "http://localhost:2112/api/datacenters/1/region" } ],

I am following a spring getting started tutorial in https://spring.io/guides/gs/accessing-data-rest/ I added another entity books that has @ManyToOne relation to Person entity. Person entity has a new property called bikes and has a @OneToMany relation with Bike entity. Only thing that is different from the getting started project is the new attribute with its getter and setter: package hello; import java.util.List; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.OneToMany;