Support JSON-B json binding as an alternative to Jackson #98

Activity

1. panga commented on Jun 23, 2018

   

   panga

   on Jun 23, 2018

   More actions

   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).
2. zootalures commented on Jun 23, 2018

   

   zootalures

   on Jun 23, 2018

   Last edited by zootalures

   MemberAuthor

   More actions

   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.

   Pull requests welcome here!
3. panga commented on Jun 23, 2018

   

   panga

   on Jun 23, 2018

   More actions

   @zootalures Indeed, that makes sense. I've created #142 about modules.

   I'll contribute with PR's soon.

   I think need #134 and #72 merged to start something on this area without too much conflicts.

   Thanks!