You would like to have custom representation types even with support of hypermedia links, so I can't imagine why #SpringHATEOAS does not allow customized ObjectMappers with "application/vnd*+json" odrotbohm@chaos.social ?

Ran into this issue with the following setup:
- REST resource extends #SpringHATEOAS RepresentationModel
- REST resource is represented with a custom application/vnd**+json content-type
The result is: Not the custom Jackson ObjectMapper is used (that has e.g JSR385 Deserializers registered) but with it's own OM instance 😕 That's not as expected

https://github.com/spring-projects/spring-framework/issues/26212#issuecomment-761076480

I released the new major version 2.0.0 of JSON:API for Spring HATEOAS, see https://github.com/toedter/spring-hateoas-jsonapi/.

Now based on Spring Boot 3.0.0 and support for JSON:API 1.1!

#spring #jsonapi #springhateoas #rest #java

#SpringHATEOAS doesn't mentions the HTTP method in its links (cf. https://spring.io/guides/gs/rest-hateoas/).

How is the user supposed to understand they need to use POST/PUT/PATCH? Do I miss something? 🤔