Similar to the ISPN dialect, there could be a "cache-per-table" approach for the Ehcache dialect. If we agree we want to have that eventually but don't manage to do it in time for the 4.1 Final, we should at least extract the following bits from the ISPN dialect and move it to a shared K/V package in core:
* {{InfinispanProperties#PERSISTENCE_STRATEGY}} should go to {{KeyValueStoreProperties}} * The {{PersistenceStrategy}} enum
Also the following should be considered:
* Establish a global option in the option system * Establish a per-entity option in the option system
|