anchor.diff:  difference is that you would specify your Hibernate ORM configuration in `META-INF/persistence.xml`:
   
   [source,xml]
  +.Example persistence.xml resource
   --
   <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence"
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  
positive.code:            -p 5432:5432 postgres:10.5
  --
  
  ====
  
  == Setting up and configuring Hibernate ORM with a `persistence.xml`
  
  Alternatively, you can set a `META-INF/persistence.xml` to setup Hibernate ORM.
  This is useful for:
  
  * migrating existing code
  
negative.code: quarkus.hibernate-orm.database.generation=drop-and-create
  --
  
  Note that these configuration properties are not the same ones as in your typical Hibernate ORM configuration file: these drive Quarkus configuration properties,
  which often will map to Hibernate configuration properties but could have different names and don't necessarily map 1:1 to each other.
  
  Also, Quarkus will set many Hibernate configuration settings automatically, and will often use more modern defaults.
  
  Please see below section <<hibernate-configuration-properties, Hibernate ORM configuration properties>> for the list of properties you can set in `{config-file}`.
  
  An `EntityManagerFactory` will be created based on the Quarkus `datasource` configuration as long as the Hibernate ORM extension is listed among your project dependencies.
  
  The dialect will be selected based on the JDBC driver - unless you set one explicitly.
  
  You can then happily inject your `EntityManager`:
  
  [source,java]
  .Example application bean using Hibernate
  --
  @ApplicationScoped
  public class SantaClausService {
  