Since HHH-17705, which was implemented to prevent issues identified during development of WFLY-18989, Hibernate ORM is now exposing a service which needs to be loaded via standard Java ServiceLoader mechanisms.

It would seem that during regular JPA usage in WildFly there is no need to make modifications to the module.xml of Hibernate ORM, but I suspect this could be a problem in case users start the ORM in other ways, not least via custom framework integrations which haven't been tested under the strict classloader isolation of WildFly.

I'm suggesting to modify the module.xml of Hibernate ORM in WildFly to ensure such users wouldn't experience any problem in finding the new service.