title: Jackson date deserialization - "invalid" day of month
body: <p>I am using <code>Spring Boot</code> with <code>Jackson</code> serializing/deserializing JSON requests/responses. I have come accross a behaviour when trying to deserialize <code>Date</code> in ISO format that I would like to avoid.</p>
  
  <p>When I use an invalid day of month or month of year, Jackson handles it by adding the extra number of days/months to the date.</p>
  
  <p>For instance</p>
  
  <pre><code>{
      "date": "2018-02-40T15:00:00+01:00"
  }
  </code></pre>
  
  <p>is deserialized as <code>Mon Mar 12 15:00:00 CET 2018</code></p>
  
  <p>Or</p>
  
  <pre><code>{
      "date": "2018-14-20T15:00:00+01:00"
  }
  </code></pre>
  
  <p>as <code>Wed Feb 20 15:00:00 CET 2019</code></p>
  
  <p>Is there a way to enforce a validation somehow? I was looking at the list of <a href="https://github.com/FasterXML/jackson-databind/wiki/Serialization-Features" rel="nofollow noreferrer">Serialization</a> and <a href="https://github.com/FasterXML/jackson-databind/wiki/Deserialization-Features" rel="nofollow noreferrer">Deserialization</a> features but I was not able to find any that could influence this behaviour.</p>
  
  <p>I am using the old Java Date API - <code>java.util.Date</code>.</p>