Spring Tips: the road to Spring Boot 3: Spring Framework 6

Hi, Spring fans! In this installment, we begin a journey to Spring Boot 3, due end of November, 2022. In this installment, we'll look - at a very high level - at some of the amazing features in Spring Framework 6, which underpins Spring Boot 3.

[slcooIj]

Great and quick overview, thx. The hints for native compilation have 'grey hair potential' ;) at the current state. Maybe this can be improved over time. I'm sure it is not that easy to be 100% safe in case of an auto determination. Let's hope the best :)

[DavidParry-Hacker]

@starbuxman what a fantastic video, the effortless right flavor to start the groking even deeper. Thank you sir!

[chandragie]

I see similarities between FeignClient and HttpServiceProxyFactory... It's a bit more complicated to do the config here tho

[ornelfranck]

This is why we test in production!!!😅😂😂😂🤣😁

[kscd]

It'd be really great if you'd use a better quality microphones. The voice sounded really cranky here in an otherwise very informative video.

[pullxdb]

please add video from Spring Batch for read Excel file and Process by microservice save in multi table in database, mapping request and response

[cywang]

May i ask your IDE fonts, it's looks very comfortable

[ashikuzzamandev]

I have a question at 2:10 minutes. You always choose the latest JDK version but why 17 for this video? :D

[skies]

The @GetExchange example does not work anymore, there were changes were methods were removed. Also, explaining how to actually test those using WebTestClient would have been very appreciated.

[benaya]

is there a way to load a file as a classpath resource? so far, nothing seems to work

[rameshk]

like wise open feign client expect here

[mihirsawant]

Hi, it's great, but is ServiceProxyFactory substitution of FeignClient and will FeignClient supported in Spring Framework 6.0 ?

[USONOFAV]

Are Spring folks aware that spring boot 2.7.3+ is having issue in Pivotal Cloud Foundry deployment?

[ogyct]

Kinda sad, we have to do all that dark magic to make native images work. To me it seems, like developers made a huge amount of work, to create JVM for which you "write once, works everywhere". And now we reverse engineer to go back to the native image.

[Boss-grjw]

This hint stuff needs to disappear before it can be seriously used in production. I feel like people would spend half of their time solving a business problem and other half of their time figuring out if the library or framework uses reflection or proxies. Now you end up testing your app in non-native environment and you are required to rerun tests against native builds as well. I would rather accept the high memory footprint until this thing gets more mature.

[yadigarcaliskan]

I don’t like such a framework which are trying to solve every problem on a very complicated way