anchor.diff:  
   == About serialization
   
  -The library we use to serialize Java objects to JSON documents is http://json-b.net/[JSON-B].
  -It uses Java reflection to get the properties of an object and serialize them.
  -
  -Using native executables with GraalVM, all classes that will be used with reflection need to be registered.
  +JSON serialization libraries use Java reflection to get the properties of an object and serialize them.
  +
  +When using native executables with GraalVM, all classes that will be used with reflection need to be registered.
   The good news is that Quarkus does that work for you most of the time.
   So far, we haven't registered any class, not even `Fruit`, for reflection usage and everything is working fine.
   
  
positive.code: It allows to reduce the size of the native executable.
  ====
  
  === Using Jackson
  
  Quarkus provides the option of using https://github.com/FasterXML/jackson[Jackson] instead of JSON-B. To do so, the `quarkus-resteasy-jsonb` dependency needs to be replaced with:
  
  [source,xml]
  ----
  <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-resteasy-jackson</artifactId>
  </dependency>
  ----
  
  When using Jackson, Quarkus allows users to customize the `ObjectMapper` very easily - all that needs to be done is to configure a CDI producer bean like so:
  
  
negative.code: No legumes there.
  
  As mentioned above, the issue is that Quarkus was not able to determine the `Legume` class will require some reflection by analyzing the REST endpoints.
  The JSON serialization library tries to get the list of fields of `Legume` and gets an empty list so it does not serialize the fields' data.
  
  [NOTE]
  ====
  At the moment, when JSON-B or Jackson tries to get the list of fields of a class, if the class is not registered for reflection, no exception will be thrown.
  GraalVM will simply return an empty list of fields.
  
  Hopefully, this will change in the future and make the error more obvious.
  