anchor.diff:  
   The idea is to provide a `@Primary` ObjectMapper.
   
  -Based on answer provided by @prabhat1790 in [issue #890](https://github.com/springfox/springfox/issues/890)
  -```java
  +Based on answer provided by @prabhat1790 in https://github.com/springfox/springfox/issues/890[issue #890]
  +
  +[source,java]
  +----
     private static final String SPRING_HATEOAS_OBJECT_MAPPER = "_halObjectMapper";
   
     @Autowired
  
positive.code:   public ObjectMapper objectMapper() {
      return springHateoasObjectMapper;
    }
  ```
  and set the order of the other bean to lowest precedence
negative.code: trivial model with one level nesting; the design choice will become clear when we realize that model attributes can be
  arbitrarily nested. Consider (pseudo code in c# for brevity)
  
  [source,csharp]
  ----
  Person {String firstName {get;set;}, String lastName {get;set;}, Category category {get;set;}}
  Category {String name {get;set;}, String description {get;}}
  ----
  
  So one could set properties
  firstName
  