anchor.diff:    public ObjectMapper objectMapper() {
       return springHateoasObjectMapper;
     }
  -```
  -and set the order of the other bean to lowest precedence+----
  +
  +and set the order of the other bean to lowest precedence.
  +
  +*Q. How do I use this library to aggregate swagger-enabled resources from multiple services?*
  +
  +A Logical explanation of how one might go about doing this is available in the https://groups.google.com/forum/#!searchin/swagger-swaggersocket/multiple/swagger-swaggersocket/g8fgSGUCrYs/A8Ms_lFOoN4J[swagger google group]
positive.code: *Q. How does one use @ModelAttribute annotation. It doesn't seem to render the model properties as scalar properties?*
  
  In order for @ModelAttribute annotated types to be inferred the properties need to be bean properties.
  Couple of observations
  
  If the intent is immutability and passing in an object, the preferred approach is to make that a request body, in which
  case the immutability will follow the rules laid out by jackson to determine what constitutes a request "view" of the
  
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
  