Make no longer mandatory setting the persistence property `provider` to `org.hibernate.ogm.jpa.Hibernate Persistence` in order to run Hibernate OGM.
We decided to enable OGM implicitly when a JDBC connection URL, a datasource and a dialect are not provided. The user can still decide not to enable OGM by setting the `hibernate.ogm.enabled property` to false.
I recently found this method, which might be useful for this:
At least we could make sure to try the OGM provider before the ORM one.
Sounds good! Thank you
The current base Hibernate ORM persistence provider is actually able to run a Hibernate OGM SessionFactory, such as the OGM one. The problem was relative to OgmServiceRegistryInitializer, that is the class responsible for providing the extra OGM services. Before this issue the services were provided if and only if the property `hibernate.ogm.enabled` was set to true. This property can be set by the user or the OGM provider. After the issue, the services are provided also if an `OGM implicit activation` is detected, such as if neither a jdbc connection URL nor a datasource nor a dialect is provided.