anchor.diff:                          User.class)));
   ----
   
  -So far so good.
  +So far so good, it works as expected.
   
   === Monitoring
   
  
positive.code: 
  === Resources
  
  Under the hood, Dropwizard uses Jersey, so the resources are just POJOs annotated with JAX-RS annotations:
  
  [source,java]
  ----
  
negative.code: }
  ----
  
  All the underlying HTTP handling is done by the framework, you have no mandatory access to request and response objects. In this case, I create a Response but I could simply return the object; however, the return code would not be the right one (201), so to have full control over it, I prefer that solution. Moreover, the 404 (Status.NOT_FOUND) is set on the response; I could throw an exception instead, and write a mapper to make an adequate response, but it's overkill.
  
  Note that injection is performed by Guice. It seems that there is a container provided with Jersey (hk2), but I didn't managed to make it work. Linking is handmade. 
  
  Dropwizard uses Jackson to serialize / deserialize the object returned to JSON, so you have nothing special to do... but you have to configure the ObjectMapper to not fail on missing properties (see http://martinfowler.com/bliki/TolerantReader.html[Tolerant Reader]).
  
  === HTTPS
  
  