[ https://issues.jboss.org/browse/AS7-1393?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-1393: ----------------------------------- Can you be more specific as to what problem this is causing? Currently, if the user sets property "hibernate.cache.infinispan.cachemanager", we add a dependency on the specified value (in which case the cache manager will be started). If an application isn't using a 2lc, they wouldn't set this property (which means the cache isn't started). I don't think that we want the Infinispan cache to be started by default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1393?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on AS7-1393: ----------------------------------- It's not causing any problem (I would have categorized this as a bug otherwise), but the current setup is not as simple as it could/should be. I thought we already agreed that we would make Infinispan the default 2nd level cache provider, instead of the Hashtable impl. We already include the requisite cache config in the default profile. Even your suggestion doesn't go far enough, I think. Here's what I'm proposing: 1. If hibernate.cache.use_second_level_cache is true, then default hibernate.cache.region.factory_class to "org.hibernate.cache.infinispan.JndiInfinispanRegionFactory". 2. If hibernate.cache.region.factory_class is "org.hibernate.cache.infinispan.JndiInfinispanRegionFactory" (whether explicit or implicit), then default hibernate.cache.infinispan.cachemanager to "java:jboss/infinispan/hibernate". So, in the end, the user should only have to set 1 property in persistence.xml (i.e. <property name="hibernate.cache.use_second_level_cache" value="true"/>) in order to use the 2nd level cache with Infinispan. That's what I mean by simple. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira