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 Traget set to
<targetTechnology id="eap" versionRange="[7,8)" />

5.3 migration notes: "One potential upgrade concern is any custom `org.hibernate.cache.spi.QueryCacheFactory` implementations. `org.hibernate.cache.spi.QueryCacheFactory` was meant as a means to allow service providers the ability to define query result caching, generally with more stale-tolerant query result invalidation handling. However, the contract also bound it to the old second level cache contracts so they had to be updated. Its responsibilities also changed so we also decided to "rename it" to
`org.hibernate.cache.spi.TimestampsCacheFactory`"

Windup rule:

When: org.hibernate.cache.spi.QueryCacheFactory is extended
Perform: See migration notes related to org.hibernate.cache.spi.TimestampsCacheFactory.