anchor.diff:      List<ToSubstitute> list;
   ----
   
  -    Need to look like this over the wire...
  +Need to look like this over the wire...
   
   [source,java]
   ----
  
positive.code: Category {String name {get;set;}, String description {get;}}
  ----
  
    So one could set properties
    firstName
    lastName
    category.name
  
    Now we don't want category to be able to set description via the operation, how do we control/specify that?
  
    it makes it hard to reason about which fields in an objects are not intended to be mutated. This is the reason we
    chose to limit it to objects that expose getters and setters.
  
  NOTE: I know spring supports fields as well, and it will fall back to fields if setters are not found
  
  [[q7]]*Q. How should we resolve multiple object mappers available as beans especially when using spring-hateoas?*
  
  A. The idea is to provide a `@Primary` ObjectMapper.
  
    Based on answer provided by @prabhat1790 in https://github.com/springfox/springfox/issues/890[issue #890]
  
  [source,java]
  ----
  
negative.code: 
  [[q2]]*Q. What is the relationship between swagger-ui and springfox-swagger-ui?*
  
  A. It can be a little confusing
  
  - Swagger Spec is a specification
  - Swagger Api - an implementation of that specification that supports jax-rs, restlet, jersey etc.
  - Springfox libraries in general - is another implementation of the specification focused on the spring based ecosystem
  - Swagger.js and Swagger-ui - Are client libraries in javascript that can consume swagger specification
  - springfox-swagger-ui - the one that you're referring to, is just packaging swagger-ui in a convenient way so that
  spring services can serve it up.
  
  [[q3]]*Q. I use GSON and don't use Jackson, What should I do?*
  
  