spring-data-rest

I've been working on a RESTful webservice with spring-data. A few days ago a special spring-data jpa REST framework was released . Now I noticed the ability to use @Version with this framework. Is this version generated by itself or do you need to do this manually? And is it possible to use @Version on it's own? (So that I don't have to change anything to my existing repositories/domain etc..) And do I need to do some extra configuration to make use of @Version? It's been a while since I posted this question but I've figured it out. I'll explain what I did so that it might be helpful to

I have a project that uses spring-data-rest, and has a dependency project that only uses Spring Data. Both projects have spring data repositories and use @EnableJpaRepositories to implement their repository interfaces, but I only want to export the repositories in the parent project. Here's my question: is there some way to configure Spring Data REST to only expose rest endpoints for resources in the parent project, without having to explicitly annotate every repository in the dependency project with @RepositoryRestResource(exported = false) ? If I can only do this with @RepositoryRestResource

I have an entity as below Class Person{ String id; String name; String numberOfHands; } With Spring Data Rest (Gosling Release Train), I'm able to specify localhost/Person?sort=name,asc for sorting name name ascending. Now, in a case where I need to sort by numberOfHands descending and name ascending. I'm able to specify localhost/Person?sort=numberOfHands,name,asc But, I'm not able to specify localhost/Person?sort=numberOfHands,desc,name,asc Is there a way to specify multiple sort order? Thanks! M. Deinum Solution (tl;dr) When wanting to sort on multiple fields you simply put the sort

I want to create a REST link for an Employee entity that will basically be a findByAllFields query. Of course this should be combined with Page and Sort . In order to do that I have implemented the following code: @Entity public class Employee extends Persistable<Long> { @Column private String firstName; @Column private String lastName; @Column private String age; @Column @Temporal(TemporalType.TIMESTAMP) private Date hiringDate; } So I would like to have lets say a query where I can do: http://localhost:8080/myApp/employees/search/all?firstName=me&lastName=self&ageFrom=20&ageTo=30

I have been looking at various examples of how to use Spring with REST . Our end target is a Spring HATEOAS/HAL setup I have seen two distinct methods for rendering REST within Spring Via @RestController within a Controller Via @RepositoryRestResource within a Repository The thing I am struggling to find is why would you use one over the other. When trying to implement HAL which is best? Our database backend is Neo4j . zpontikas Ok, so the short story is that you want to use the @RepositoryRestResource since this creates a HATEOAS service with Spring JPA . As you can see here adding this