nispan test code, and potentially the Infinispan provider itself?
Thanks,
Chris Dennis
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
from the
RefreshUpdatedDateTest, and the only reason this test passes for the non-strict
elements is because the read-write elements are in the annotated class array
first, and so everyone ends up using the read-write access strategy.
> On May 24, 2016, at 2:19 PM, Chris Dennis wrote:
>
Tell a lie… it’s now sensitive to the iteration order of the entityBindingMap
(a HashMap) in MetadataImpl. Regardless, modifying that test to give each
entity it’s own region causes the non-strict entities to start failing.
> On May 26, 2016, at 2:58 PM, Chris Dennis wrote:
>
&g
+1. From my point of view this makes sense.
I’ll need to confer with higher-ups about what we would then do regarding our
copy of the Ehcache 2.x provider and whether we want to port it across to the
new SPI. That should in principle be a separate discussion, but I’m a little
too heads-down in
