[ http://opensource.atlassian.com/projects/hibernate/browse/OGM-4?page=com.... ] Sanne Grinovero commented on OGM-4: ----------------------------------- The way the Infinispan defines the default configuration is the most general-purpose possible. When not found so, we can suggest a change in default configuration. So we should argue if "general-purpose" in the universe of Infinispan applications is different than "general-purpose" in the context of OGM applications. In which ways? - a Transaction Manager would be highly recommended, but you inject that already. - batching? it's disabled by default, but The Lucene Directory requires batching as it uses it. OGM could likely benefit as well from it, but depending if you make use of it. - shutdown? you close the CacheManager at SF.close() right? alternatively a JVM shutdown hook can be registered. - fetchInMemoryState likely needs to be set to true, unless a shared persistent store is enabled. - lazyDeserialization is false, looks good to me. - L1 is disabled, likely the best option as invalidating remote L1 values is not complete so it might bring some complexity - isolationLevel I guess READ_COMMITTED (default) is fine as well - jmxStatistics we can enable this, but will require a name I think I'll write a very short one: - enable jmsStats - define at least an additional cache to be used by Lucene DirectoryProvider (actually, to share the cachemanager we should find a way to pass the instance over to the DirectoryProvider instance) - enable batching - change the name of the JGroups configuration file so that it won't conflict with other apps -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira