You can find here a possible solution for this issue: https://github.com/fax4ever/hibernate-ogm/commits/1523-wildfly-14.
Where I applied the patch I found here https://issues.jboss.org/browse/WFNOSQL-28.
Moreover, in order to be succeeded all the tests, I had to skip at all the use of the wildfly modules provided by Hibernate ORM and Hibernate Search projects, using in their place those already provided by WildFly itself.
The main reason for that is the fact, I think, that the jipijapa module could be *potentially compatible* just with a sigle version of WildFly.
For instance the Hiberante ORM modules org.hibernate:hibernate-orm-jbossmodules:5.3.6.Final contain the Jipijapa module org.hibernate.orm.jipijapa-hibernate5:5.3.6.Final, that uses the jar org.wildfly:jipijapa-hibernate5:13.0.0.Final, which in turn works well with WildFly 13, but not with WildFly 14.
For these reasons I opened this issue on ORM: https://hibernate.atlassian.net/browse/HHH-13030.
Even if the issue itself doesn't deeply solve the problem, it just switches the compatibility from WF 13 to WF 14.