This is my first time working with HATEOAS everyone and I have come to a screeching halt. Here is my problem, I have an app that converts text from a text area to a pdf and a pdf to images. My issue is that I send both back as a ResponseEntity<byte[]>. Here is a sample success response from the text
Tag: spring-hateoas
Migrate builder to Spring hateoas 2.6.7
I have this old code implemented in hateoas:1.0 I updated my code to hateoas 2.6.7 but the code is changed this way: What is the proper way to implement this change? I tried this: But it’s not clear how I have to implement the code that I can send affordances. Can you advice what is the proper way to implement
Return link from Hateos
I have this old Spring Hateos code which I want to migrate to the latest version: I tried this: I get error at this line: Can you advise what is the correct way to implement this? Answer Based on your comments & question for migration this is what I am suggesting: …. //calling addLinlk And inside addLink: Tested with Java
How do you replace sub entities with HATEOAS links?
I am trying to figure out how to process a series of results in my controller, yet still return links for inline sub resources. when I hit the exposed repository endpoint, I get responses that look like the following: however when I hit my cached version of the entity, I get the following any idea how I can return something
“org.springframework.data.util.TypeInformation.getActualType()” because “propertyType” is null
A Spring Boot 2.5.1 application is logging this warning: whereas Spring Boot 2.4.4 does not. The POJO is trivial: and the Spring RestController is similarly: To trigger the warning submit a POST: The warning is triggered while “handling” the _links property of the EntityModel<SoPojo> but why and what can I do about it. Any ideas? Update: As dkb notes, this
Gradle Not Honoring Forced Dependency Version
I am unable to force a version of a dependency using Gradle. My goal is to use version 0.20.0.RELEASE of the Spring HATEOAS library, but despite all my efforts it keeps resolving to 0.19.0.RELEASE. I have attempted a number of strategies, both in isolation and in combination with one another. These strategies include, but are possibly not limited to, the