|
|
|
|
|
by ragnese
2199 days ago
|
|
My experience has been that there might actually be MORE boilerplate now than when I did ad-hoc translation to/from JsonObject. inline classes straight-up don't work with Jackson, and probably never will. So for every class that has a field that is an inline class, I have to write a "builder class" that's exactly the same except replacing the inline class with the class it wraps. Also, @JsonUnwrapped doesn't work with Kotlin. And, of course, doing anything with generics is a complex nightmare with Jackson (because of JVM's type erasure). Not to mention, all these failures happen at runtime, so you don't even know your class is going to be a problem until you run the code. The whole thing just sucks and I actually miss the simplicity of translating by hand... |
|