Ok but I'm not sure which harm it would do, assuming that:

• it would necessarily need to be the only implementation which we discover
• it would be validated by the fact that - whatever your implementation of choice - we'll need some additional options

For example, MongoDB won't work unless you have defined also hibernate.ogm.datastore.database .. if the user gave an Infinispan configuration option that wouldn't work. That's why in the comment from last May I made the example of an URL as an ideal solution: no chances for looking for the wrong properties and ultimately resulting into a confusing error message.

So it's just about avoiding to have to specify a redundant property. It's redundant because - for example in the WildFly case - I've already specified in the dependency section of my application that it needs to use/access the MongoDB dialect.

Either way, it's very confusing that it defaults to try loading the Infinispan backend - and fail hard with a cryptic error - when all I have on classpath is a MongoDB backend and have correctly set the required properties for MongoDB.