Tatu Saloranta
Tatu Saloranta
Sounds like a Spring problem: please use Spring forums for asking help. Otherwise, we would need a stand-alone (no external dependencies) reproduction of the problem, showing exactly what is being...
Ok so: 1. Functionality used via annotations is defined elsewhere (even in case of regular `@JsonView`, handling provided by jackson-databind, so this request would only be for specific change to...
Quick note: yes, I have occasionally thought about such a thing, but no, nothing implemented. Afterburner and Blackbird are sort of half of the puzzle: to remove runtime use of...
Looks like there has been some work committed to Quarkus: would be nice to have links from here to outcomes, docs, if possible? (sounds like serialization-side opt-in optimization feature flag...
Ok thank you for sharing @mariofusco !
Inconsistency between @JsonInclude and ObjectMapper.setDefaultPropertyInclusion() for default values
While I can understand confusion between usage -- that of annotation a POJO vs other use (annotating property or setting default inclusion -- this difference is intentional and by design...
Wrong repo since there's XML-specific parts. However, I doubt this can be implemented -- problem being that POJOs like `LocationID` cannot really be included as attributes in general; there is...
@apjoseph Unfortunately the big problem here is that conversion requires both reading and writing, and `ObjectReader` can only do former but not latter. Same problem affects `ObjectWriter`. So... I agree...
I think adding more methods in `ObjectMapper` is a slippery slope and I would prefer going via `ObjectReader` route. And I definitely would not want to expose `SerializerProvider` (or `DeserializationContext`)....
Minor progress was addition of: public T treeToValue(TreeNode n, Class valueType); in `ObjectReader` for 2.13. So `JsonNode` can be converted. There is the sort of matching method in `DeserializationContext`: public...