spring-data-rest

Using Spring Data REST with JPA in version 2.1.0. How can I configure the pagination in order to have the page argument starting at index 1 instead of 0 ? I have tried setting a custom HateoasPageableHandlerMethodArgumentResolver with an mvc:argument-resolvers , but that doesn't work: <mvc:annotation-driven> <mvc:argument-resolvers> <bean class="org.springframework.data.web.HateoasPageableHandlerMethodArgumentResolver"> <property name="oneIndexedParameters" value="true"/> </bean> </mvc:argument-resolvers> </mvc:annotation-driven> Note that this behaviour is perfectly coherent with the

There is a use case I am struggling with SDR as below - THere is User Table and RefSecQuestion tables User -> ManyTOOne -> RefSecQuestion , RefSecQuestion -> OneToMany -> User THere is User Table and UserFriends tables User -> OneToMany UserFriends , UserFriends -> ManyToOne -> User There is a requirement that when I go /users/{id}/userFriends , then firstname , lastname etc from UserProjection should be shown by default As a result, I enabled excerptProjection in UserRepository and it works fine. I expect about 100 results here so that is fine if this result is not paginated. But , now since

I am trying to add @NotNull constraint into my Person object but I still can @POST a new Person with a null email. I am using Spring boot rest with MongoDB. Entity class: import javax.validation.constraints.NotNull; public class Person { @Id private String id; private String username; private String password; @NotNull // <-- Not working private String email; // getters & setters } Repository class: @RepositoryRestResource(collectionResourceRel = "people", path = "people") public interface PersonRepository extends MongoRepository<Person, String> { } Application class: @SpringBootApplication

Wanted to know how is @Version annotation in Spring Data REST put to use for ETags, I do not see the ETags populated for some reason @Entity @EntityListeners(AuditingEntityListener.class) public class Venue implements Serializable { private static final long serialVersionUID = -5516160437873476233L; private Long id; ... // other properties private Long version; private Date lastModifiedDate; // getters & setters @JsonIgnore @LastModifiedDate public Date getLastModifiedDate() { return lastModifiedDate; } @Version @Column public Long getVersion() { return version; } Going by the docs this should

I have a project based on spring-data-rest and also it has some custom endpoints. For sending POST data I'm using json like { "action": "REMOVE", "customer": "http://localhost:8080/api/rest/customers/7" } That is fine for spring-data-rest, but does not work with a custom controller. for example: public class Action { public ActionType action; public Customer customer; } @RestController public class ActionController(){ @Autowired private ActionService actionService; @RestController public class ActionController { @Autowired private ActionService actionService; @RequestMapping(value = "/customer

I use Spring Data Rest 2.1.1 Release with the default configuration. Considering the following resource: GET /communities/MyCommunity { "creationDate": "2014-07-16T06:22:37.153+0000", "name": "GroupeSEB", "_links": { "self": { "href": "http://localhost:8080/api/communities/GroupeSEB" }, "posts": { "href": "http://localhost:8080/api/communities/GroupeSEB/posts" } } } When I get the "posts" sub-resource : GET /communities/MyCommunity/posts { "_embedded": { "posts": [ { "creationDate": "2014-07-09T13:09:14.535+0000", "id": "53bd3efae4b012818368c549", "_links": { "self": { "href": "http:/

Since version 2.5.7 Spring Data REST does not properly perform a PUT request to update resource which has associated resources . Unlike PATCH request that works as expected! For example, Person has a many-to-one association with Addres . If we perform a PUT request with SDR v.2.5.6 (Spring Boot v.1.4.3) then all works OK. But if we switch to version 2.5.7 (i.e. to Spring Boot v.1.4.4) then we get an error: Can not construct instance of Address: no String-argument constructor/factory method to deserialize from String value The same happens with other types of associations, for example with one