Dan thanks for another wonderful insight about RestClient. Only expectation from many developers is Spring Boot can provide the necessary Infrastructure to support commonly used interceptors under the hood such as JWT token propagation, Oauth related mechanisms..etc. Webclient already has such functionality through builder pipeline. Hope this could be considered in future release for RestClient
Thank you Dan for uploading the tutorial. This is very helpful. Simple use case wherein we can use this: Logging request type, url and response time which is very useful while debugging something in production. For me, something more to explore: Understanding how rest client interceptor behaves when we get 4xx, 5xx and timeout errors.
Thanks Dan for your videos!! Very excited about the new Rest Client in 3.2, so appreciate your various tutorials about it... For a long time everyone was saying that the RestTemplate is going to be deprecated (which now doesn't really seem true any more right?), so we moved on to using the WebFlux WebClient in every new project. To be honest I was never really happy about it, it always kind of felt wrong to use a reactive tool and just tack on a '.block()' to use it synchronously.... 😉 But now with the Rest Client it seems we have a nice and modern alternative again that I will try to advocate for in our new projects! On a side note, do you happen to know if Spring Boot 3.2 supports automatic Observability instrumentation for the Rest Client like it does for the WebClient? We just started just using Observability in our projects and this would be great...
Thanks for the video. Do you have any documentation link on how to use interceptors to deal with authencation based on tokens that need to be refreshed after expires?
Thank you. The interceptor is null. I created the RestClient via @Bean and passing the custom interceptor annotated as @component. Why is the @RestClient Bean is seeing the interceptor as null ?. Isn't the component interceptor in a state to be available to the @Bean RestTemplate?
Thank you for the video Dan! Is it possible to read the response body of the interceptor? I was trying to read the response body but I was not able to do that. ClientHttpResponse response = execution.execute(request, body); Does anyone know how to do it? Assume that for auditing purpose I want to save in the database the request details and the response details (headers, path variables, query params, response body etc.) Thank you in advance!
Hi Dan, this is a bit more advanced, thanks… it’s nice to see this type of content in a sea of hello world examples which take you nowhere. ❤
Dan thanks for another wonderful insight about RestClient. Only expectation from many developers is Spring Boot can provide the necessary Infrastructure to support commonly used interceptors under the hood such as JWT token propagation, Oauth related mechanisms..etc. Webclient already has such functionality through builder pipeline. Hope this could be considered in future release for RestClient
Rest client will be my main topic for February! Thank you Dan
Thx, Dan for this video!
Thank you Dan for uploading the tutorial. This is very helpful.
Simple use case wherein we can use this: Logging request type, url and response time which is very useful while debugging something in production.
For me, something more to explore:
Understanding how rest client interceptor behaves when we get 4xx, 5xx and timeout errors.
Thanks dan for sharing the knowledge. Really helpful!!
Thanks Dan for your videos!! Very excited about the new Rest Client in 3.2, so appreciate your various tutorials about it... For a long time everyone was saying that the RestTemplate is going to be deprecated (which now doesn't really seem true any more right?), so we moved on to using the WebFlux WebClient in every new project. To be honest I was never really happy about it, it always kind of felt wrong to use a reactive tool and just tack on a '.block()' to use it synchronously.... 😉 But now with the Rest Client it seems we have a nice and modern alternative again that I will try to advocate for in our new projects!
On a side note, do you happen to know if Spring Boot 3.2 supports automatic Observability instrumentation for the Rest Client like it does for the WebClient? We just started just using Observability in our projects and this would be great...
Thanks for the video. Do you have any documentation link on how to use interceptors to deal with authencation based on tokens that need to be refreshed after expires?
Very informative
Thank you Dan
Thank you.. it is very helpful
Thanks for the video.
Thank you. The interceptor is null. I created the RestClient via @Bean and passing the custom interceptor annotated as @component. Why is the @RestClient Bean is seeing the interceptor as null ?. Isn't the component interceptor in a state to be available to the @Bean RestTemplate?
Thank you for the video Dan! Is it possible to read the response body of the interceptor?
I was trying to read the response body but I was not able to do that.
ClientHttpResponse response = execution.execute(request, body);
Does anyone know how to do it? Assume that for auditing purpose I want to save in the database the request details and the response details (headers, path variables, query params, response body etc.)
Thank you in advance!
What about a global response interceptor - for example to log a certain header.
Hey Dan, do you have paid courses in plateforms like Pluralsight or Udemy?
in some.videos you're a java champion and in others a spring developer, what is your secret identity?
Nice video!!
The link for github are wrong