One minor glitch I stumbled upon while implementing Spring Infinispan:
final DefaultCacheManager cm = new DefaultCacheManager(false);
cm.start();
assertEquals(ComponentStatus.RUNNING, cm.getStatus());
fails with
java.lang.AssertionError: expected:<RUNNING> but was:<INSTANTIATED>
since you need to call getCache() or getCache(name) before
DefaultCacheManager is actually started.
Obviously not a big deal, but it arguably doesn't follow the principle
of least surprise. Is it worth doing something about it?
Cheers,
Olaf
_______________________________________________
infinispan-dev mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/infinispan-dev