title: ModelMapper: Mix implicit and explicit mapping?
body: <p>In order to write the minimum amount of code required, I'm trying to let ModelMapper generate its implicit mapping and only write explicit property mappings for those properties that it couldn't auto-map.</p>
  
  <p>If I let ModelMapper generate an implicit mapping using:</p>
  
  <pre><code>modelMapper.createTypeMap(SourceType.class, DestType.class);
  </code></pre>
  
  <p>it complains about <code>setSomeId</code> having multiple possible mappings. I then tried to fix just that using:</p>
  
  <pre><code>modelMapper.addMappings(new PropertyMap&lt;SourceType, DestType&gt;() {
      protected void configure() {
          map().setSomeId(source.getProperty().getWeirdID());
      }
  });
  </code></pre>
  
  <p>However, I found that ModelMapper still complains, because an exception is actually thrown on <code>createTypeMap</code>, so it doesn't have a chance to reach my custom mapping code. </p>
  
  <p>If I invert both statements, I get an error:</p>
  
  <blockquote>
    <p>java.lang.IllegalStateException: A TypeMap already exists for class SourceType and class DestType</p>
  </blockquote>
  
  <p>If I leave out <code>createTypeMap</code> completely, ModelMapper complains about missing mappings for all other properties of the <code>DestType</code> (those who it was able to map automatically with <code>createTypeMap</code>).</p>
  
  <p>I found no explicit clue in the Documentation whether mixing implicit with explicit mappings is supported and how it's done.</p>
  
  <p>Can anyone help?</p>