You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think JSON-B API is a better choice to remove thirdparty library dependencies from core, to be honest Jackson Databind adds to much overhead that isn't needed. I think it will remove at least 1mb of JARs compared to Yasson (JSON-B RI).
We designed for this case (JSON-B was released around the same time originally wrote the FDK ) - input/output corecions should support being moved to modules - we chose Jackson initially because it was more widely supported and understood - the way to do this is to :
Move the Jackson code into a module (e.g. fdk-java-jackson)
Add a new module for JSON-B to the FDK
(optionally) refactor flow client to juse JSON-B vs Jackson
We are also working on cloudevents/JSON codec #134 support - that would mean chosing one or other as the basis for reading incoming event data there.
I want to be able to use JSON-B as an alternative to Jackson for JSON marshalling
Is one or other included by default? Can i switch between marshalling by adding a module to my function?
The text was updated successfully, but these errors were encountered: