As far as 2LC is concerned, this is not problematic for 2LC users because except in
testing, we never check this value in the production code. IOW, in production we set max
entries but we don't query it, so it's not problematic. In testing, we verify that
the cache's eviction max entries is the one we've configured via the Hibernate/JPA
configuration, but that's it.
On 15 May 2015, at 16:38, Scott Marlow <smarlow(a)redhat.com>
wrote:
Applications that compile against Infinispan 6.x, will expect that
org.infinispan.configuration.cache.EvictionConfiguration.maxEntries()
returns an int but when they run against Infinispan 7.x, they will not
find this method (since maxEntries() returns a long).
Is this a known bug or issue on Infinispan 7.x? Can you recommend a
solution or workaround for applications that currently depend on
maxEntries returning an int but aren't ready to recompile against
Infinispan 7?
Also see the original discussion from last night on hibernate-dev ml [1][2].
Scott
[1]
http://lists.jboss.org/pipermail/hibernate-dev/2015-May/012715.html
[2]
http://lists.jboss.org/pipermail/hibernate-dev/2015-May/012725.html
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com