EAP 7.2 Migration: Hibernate ORM 5.1 to Hibernate ORM 5.3 App Migration - Schema management tooling

Documentation (preview) about the[ issue:|https://doc-stage.usersys.redhat.com/documentation/en-us/jboss_enterprise_application_platform_continuous_delivery/14/html-single/migration_guide/#migrating_from_hibernate_5_1_to_5_3
]

An abstract (yet working) Hibernate 5.3 PoC rule may be found at https://github.com/emmartins/windup-rulesets/blob/WINDUPRULE-372/rules-reviewed/eap7/eap71/hibernate51-53.windup.xml , which should be broken into multiple rules targeting each concrete Hibernate 5.3 migration issue at https://github.com/hibernate/hibernate-orm/blob/5.3/migration-guide.adoc

Note the example rule reference above should have the EAP Target set to
<targetTechnology id="eap" versionRange="[7,8)" />

== Changes to schema management tooling

In 5.2.3, "a new strategy for retrieving database tables was introduced that improves SchemaMigrator and SchemaValidator
performance. This strategy executes a single `java.sql.DatabaseMetaData#getTables(String, String, String, String[])`
call to determine if each `javax.persistence.Entity` has a mapped database table.
This strategy is the default, and uses the property setting `hibernate.hbm2ddl.jdbc_metadata_extraction_strategy=grouped`.
This strategy may require `hibernate.default_schema` and/or `hibernate.default_catalog` to be provided."

Windup rule:

When: if neither hibernate.default_schema nor hibernate.default_catalog are defined, schema management tooling may not work properly
Perform: define hibernate.default_schema or hibernate.default_catalog (whichever is used by the selected dialect), or, alternatively, set hibernate.hbm2ddl.jdbc_metadata_extraction_strategy=individually.