title: Correct way to handle abstract entities with JPARepositories?
body: <p>I have a bunch of tables with exactly same columns, let's say, ID, NAME, DESCRIPTION. For legacy reasons I cannot change these tables.</p>
  
  <p>In my models, I created an abstract super class for these, using the @MappedSuperclass annotation. I then created a repository for it:</p>
  
  <pre><code>JpaRepository&lt;MyAbstractEntity, Long&gt;
  </code></pre>
  
  <p>But this doesn't seem to work with JPARepository (or rather Hibernate?) as it's not a real entity.</p>
  
  <p>So what is the preferred way to deal with such a hierarchy?</p>