On 08/18/2015 01:10 PM, Sanne Grinovero wrote: > I think such options should not be an aspect of the Cache > configuration but only a property of the Hibernate configuration.
The time to do that would of been about four years ago (now we have to be configuration compatible on the WildFly side at least). Still, not all applications include Hibernate configuration settings but they do expect to use a second level cache. If we were to remove the Hibernate section from [1], where would that configuration live and what code would deal with that? > > Why should that be known to the Infinispan configuration? In WildFly, that happens to be where we start/stop Infinispan caches, which makes sense since that is where we also deal with clustering. > > > On 18 August 2015 at 14:29, Scott Marlow <smar...@redhat.com> wrote: >> I didn't know about 'immutable-entity', should that be listed in [1] for >> the WildFly standalone*.xml, so users can configure 'immutable-entity'? >> >> [2] describes the possible Infinispan subsystem settings for [1]. >> >> Scott >> >> [1] >> https://github.com/wildfly/wildfly/blob/master/clustering/infinispan/extension/src/main/resources/subsystem-templates/infinispan.xml#L39 >> >> [2] >> https://github.com/wildfly/wildfly/blob/master/clustering/infinispan/extension/src/main/resources/schema/jboss-as-infinispan_4_0.xsd >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
