A more useful variation would be to allow passing in a pre-constructed Infinispan CacheManager: in that case the user would also be free to use a programmatic API, WDYT?

When running on WildFly I'd want it to reuse the existing JGroups channel, but start (and manage) its own CacheManager so that we can configure it ourselves. also such an approach could lead us to limit the amount of configuration options to the ones which make sense to OGM.. great simplification for the user.

Also consider that Infinispan's strategies to boot up have been changing wildly and will change again, we probably don't want to couple ourselves too much on this.