Action Jackson! Effective JSON processing in Spring Boot Applications by Joris Kuipers @ Spring I/O

  Рет қаралды 11,984

Spring I/O

Spring I/O

Күн бұрын

Пікірлер: 16
@AmitKumaarrr
@AmitKumaarrr Жыл бұрын
Everyone uses json, but few videos about it. Thank you so much.
@aman211275
@aman211275 Жыл бұрын
Excellent talk!! I really enjoyed it. Thank you Joris!
@EmmanuelOladipupo-p7k
@EmmanuelOladipupo-p7k Жыл бұрын
Excellent. Thank you Joris.
@faelperetta
@faelperetta Жыл бұрын
Very good talk where whe can see the interesting options we have to customaize the JSON serialization and deserialization
@ivandenysenko
@ivandenysenko Жыл бұрын
Great talk. Thanks for sharing your experience.
@kevinnguyen163
@kevinnguyen163 Жыл бұрын
Excellent! Thank you for such a great talk.
@MohammedKamil
@MohammedKamil Жыл бұрын
This is a very good talk for me, who's getting introduced to java and spring boot
Жыл бұрын
I can think on one reason to create an ObjectMapper instance without the builder: a client library (Do not want user configuration mess up your requests)
@Quip76
@Quip76 Жыл бұрын
Yes, in the context of the talk I was referring to regular application code only: of course there are always reasons to not use Boot ;)
@USONOFAV
@USONOFAV Жыл бұрын
Does the new library passes all CVE vulnerabilities?
@rydmerlin
@rydmerlin Жыл бұрын
As you demonstrated the parameters example I was thinking what happens when folks use any kind of code obfuscation.
@Quip76
@Quip76 Жыл бұрын
Obfuscation and reflection are not exactly friends, indeed: better to be explicit about everything, then
@konstantingromov6485
@konstantingromov6485 Жыл бұрын
Great talk (e.g. I didn't know about Views - seems sort of custom graphql can be implemented using it :). @Joris, I have a question - is it possible to configure properly serialization/deserialization with lombok delegate feature ( lombok.experimental.Delegate) - or fields should always be present on the target class?
@Quip76
@Quip76 Жыл бұрын
I'm not familiar with the particular Lombok feature, but in general I'd say that as long as you stick to property accessors (i.e. getters and setters) and constructors rather than direct field access it should all just be transparent
@rydmerlin
@rydmerlin Жыл бұрын
Even if you create an objectmapper in the controller. How do you ensure endpoints in that controller will use it?
@Quip76
@Quip76 Жыл бұрын
It wouldn’t be very typical to do that in a controller if you rely on the framework to do the (un)marshalling for you. You’d rather configure the relevant HTTP message converter to use your custom ObjectMapper
Bootiful Spring Boot 3 by Josh Long @ Spring I/O 2023
49:44
Spring I/O
Рет қаралды 26 М.
When you have a very capricious child 😂😘👍
00:16
Like Asiya
Рет қаралды 18 МЛН
Chain Game Strong ⛓️
00:21
Anwar Jibawi
Рет қаралды 41 МЛН
When you have a very capricious child 😂😘👍
00:16
Like Asiya
Рет қаралды 18 МЛН